Commit 198266af authored by Jonathan Neuschäfer's avatar Jonathan Neuschäfer Committed by Jonathan Corbet
Browse files

Documentation/arm/sa1100: Remove some obsolete documentation



The support for the following boards, among others, was removed in 2004
with commit "[ARM] Remove broken SA1100 machine support.":

- ADS Bitsy
- Brutus
- Freebird
- ADS GraphicsClient Plus
- ADS GraphicsMaster
- Höft & Wessel Webpanel
- Compaq Itsy
- nanoEngine
- Pangolin
- PLEB
- Yopy

Tifon support has been removed in 2.4.3.3.

Signed-off-by: default avatarJonathan Neuschäfer <j.neuschaefer@gmx.net>
Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
parent 6a241a11
Loading
Loading
Loading
Loading
+0 −51
Original line number Diff line number Diff line
===============================
ADS Bitsy Single Board Computer
===============================

(It is different from Bitsy(iPAQ) of Compaq)

For more details, contact Applied Data Systems or see
http://www.applieddata.net/products.html

The Linux support for this product has been provided by
Woojung Huh <whuh@applieddata.net>

Use 'make adsbitsy_config' before any 'make config'.
This will set up defaults for ADS Bitsy support.

The kernel zImage is linked to be loaded and executed at 0xc0400000.

Linux can  be used with the ADS BootLoader that ships with the
newer rev boards. See their documentation on how to load Linux.

Supported peripherals
=====================

- SA1100 LCD frame buffer (8/16bpp...sort of)
- SA1111 USB Master
- SA1100 serial port
- pcmcia, compact flash
- touchscreen(ucb1200)
- console on LCD screen
- serial ports (ttyS[0-2])
  - ttyS0 is default for serial console

To do
=====

- everything else!  :-)

Notes
=====

- The flash on board is divided into 3 partitions.
  You should be careful to use flash on board.
  Its partition is different from GraphicsClient Plus and GraphicsMaster

- 16bpp mode requires a different cable than what ships with the board.
  Contact ADS or look through the manual to wire your own. Currently,
  if you compile with 16bit mode support and switch into a lower bpp
  mode, the timing is off so the image is corrupted.  This will be
  fixed soon.

Any contribution can be sent to nico@fluxnic.net and will be greatly welcome!
+0 −69
Original line number Diff line number Diff line
======
Brutus
======

Brutus is an evaluation platform for the SA1100 manufactured by Intel.
For more details, see:

http://developer.intel.com

To compile for Brutus, you must issue the following commands::

	make brutus_config
	make config
	[accept all the defaults]
	make zImage

The resulting kernel will end up in linux/arch/arm/boot/zImage.  This file
must be loaded at 0xc0008000 in Brutus's memory and execution started at
0xc0008000 as well with the value of registers r0 = 0 and r1 = 16 upon
entry.

But prior to execute the kernel, a ramdisk image must also be loaded in
memory.  Use memory address 0xd8000000 for this.  Note that the file
containing the (compressed) ramdisk image must not exceed 4 MB.

Typically, you'll need angelboot to load the kernel.
The following angelboot.opt file should be used::

	base 0xc0008000
	entry 0xc0008000
	r0 0x00000000
	r1 0x00000010
	device /dev/ttyS0
	options "9600 8N1"
	baud 115200
	otherfile ramdisk_img.gz
	otherbase 0xd8000000

Then load the kernel and ramdisk with::

	angelboot -f angelboot.opt zImage

The first Brutus serial port (assumed to be linked to /dev/ttyS0 on your
host PC) is used by angel to load the kernel and ramdisk image. The serial
console is provided through the second Brutus serial port. To access it,
you may use minicom configured with /dev/ttyS1, 9600 baud, 8N1, no flow
control.

Currently supported
===================

	- RS232 serial ports
	- audio output
	- LCD screen
	- keyboard

The actual Brutus support may not be complete without extra patches.
If such patches exist, they should be found from
ftp.netwinder.org/users/n/nico.

A full PCMCIA support is still missing, although it's possible to hack
some drivers in order to drive already inserted cards at boot time with
little modifications.

Any contribution is welcome.

Please send patches to nico@fluxnic.net

Have Fun !
+0 −25
Original line number Diff line number Diff line
========
Freebird
========

Freebird-1.1 is produced by Legend(C), Inc.
`http://web.archive.org/web/*/http://www.legend.com.cn`
and software/linux maintained by Coventive(C), Inc.
(http://www.coventive.com)

Based on the Nicolas's strongarm kernel tree.

Maintainer:

Chester Kuo
	- <chester@coventive.com>
	- <chester@linux.org.tw>

Author:

- Tim wu <timwu@coventive.com>
- CIH <cih@coventive.com>
- Eric Peng <ericpeng@coventive.com>
- Jeff Lee <jeff_lee@coventive.com>
- Allen Cheng
- Tony Liu <tonyliu@coventive.com>
+0 −102
Original line number Diff line number Diff line
=============================================
ADS GraphicsClient Plus Single Board Computer
=============================================

For more details, contact Applied Data Systems or see
http://www.applieddata.net/products.html

The original Linux support for this product has been provided by
Nicolas Pitre <nico@fluxnic.net>. Continued development work by
Woojung Huh <whuh@applieddata.net>

It's currently possible to mount a root filesystem via NFS providing a
complete Linux environment.  Otherwise a ramdisk image may be used.  The
board supports MTD/JFFS, so you could also mount something on there.

Use 'make graphicsclient_config' before any 'make config'.  This will set up
defaults for GraphicsClient Plus support.

The kernel zImage is linked to be loaded and executed at 0xc0200000.
Also the following registers should have the specified values upon entry::

	r0 = 0
	r1 = 29	(this is the GraphicsClient architecture number)

Linux can  be used with the ADS BootLoader that ships with the
newer rev boards. See their documentation on how to load Linux.
Angel is not available for the GraphicsClient Plus AFAIK.

There is a  board known as just the GraphicsClient that ADS used to
produce but has end of lifed. This code will not work on the older
board with the ADS bootloader, but should still work with Angel,
as outlined below.  In any case, if you're planning on deploying
something en masse, you should probably get the newer board.

If using Angel on the older boards, here is a typical angel.opt option file
if the kernel is loaded through the Angel Debug Monitor::

	base 0xc0200000
	entry 0xc0200000
	r0 0x00000000
	r1 0x0000001d
	device /dev/ttyS1
	options "38400 8N1"
	baud 115200
	#otherfile ramdisk.gz
	#otherbase 0xc0800000
	exec minicom

Then the kernel (and ramdisk if otherfile/otherbase lines above are
uncommented) would be loaded with::

	angelboot -f angelboot.opt zImage

Here it is assumed that the board is connected to ttyS1 on your PC
and that minicom is preconfigured with /dev/ttyS1, 38400 baud, 8N1, no flow
control by default.

If any other bootloader is used, ensure it accomplish the same, especially
for r0/r1 register values before jumping into the kernel.


Supported peripherals
=====================

- SA1100 LCD frame buffer (8/16bpp...sort of)
- on-board SMC 92C96 ethernet NIC
- SA1100 serial port
- flash memory access (MTD/JFFS)
- pcmcia
- touchscreen(ucb1200)
- ps/2 keyboard
- console on LCD screen
- serial ports (ttyS[0-2])
  - ttyS0 is default for serial console
- Smart I/O (ADC, keypad, digital inputs, etc)
  See http://www.eurotech-inc.com/linux-sbc.asp for IOCTL documentation
  and example user space code. ps/2 keybd is multiplexed through this driver

To do
=====

- UCB1200 audio with new ucb_generic layer
- everything else!  :-)

Notes
=====

- The flash on board is divided into 3 partitions.  mtd0 is where
  the ADS boot ROM and zImage is stored.  It's been marked as
  read-only to keep you from blasting over the bootloader. :)  mtd1 is
  for the ramdisk.gz image.  mtd2 is user flash space and can be
  utilized for either JFFS or if you're feeling crazy, running ext2
  on top of it. If you're not using the ADS bootloader, you're
  welcome to blast over the mtd1 partition also.

- 16bpp mode requires a different cable than what ships with the board.
  Contact ADS or look through the manual to wire your own. Currently,
  if you compile with 16bit mode support and switch into a lower bpp
  mode, the timing is off so the image is corrupted.  This will be
  fixed soon.

Any contribution can be sent to nico@fluxnic.net and will be greatly welcome!
+0 −60
Original line number Diff line number Diff line
========================================
ADS GraphicsMaster Single Board Computer
========================================

For more details, contact Applied Data Systems or see
http://www.applieddata.net/products.html

The original Linux support for this product has been provided by
Nicolas Pitre <nico@fluxnic.net>. Continued development work by
Woojung Huh <whuh@applieddata.net>

Use 'make graphicsmaster_config' before any 'make config'.
This will set up defaults for GraphicsMaster support.

The kernel zImage is linked to be loaded and executed at 0xc0400000.

Linux can  be used with the ADS BootLoader that ships with the
newer rev boards. See their documentation on how to load Linux.

Supported peripherals
=====================

- SA1100 LCD frame buffer (8/16bpp...sort of)
- SA1111 USB Master
- on-board SMC 92C96 ethernet NIC
- SA1100 serial port
- flash memory access (MTD/JFFS)
- pcmcia, compact flash
- touchscreen(ucb1200)
- ps/2 keyboard
- console on LCD screen
- serial ports (ttyS[0-2])
  - ttyS0 is default for serial console
- Smart I/O (ADC, keypad, digital inputs, etc)
  See http://www.eurotech-inc.com/linux-sbc.asp for IOCTL documentation
  and example user space code. ps/2 keybd is multiplexed through this driver

To do
=====

- everything else!  :-)

Notes
=====

- The flash on board is divided into 3 partitions.  mtd0 is where
  the zImage is stored.  It's been marked as read-only to keep you
  from blasting over the bootloader. :)  mtd1 is
  for the ramdisk.gz image.  mtd2 is user flash space and can be
  utilized for either JFFS or if you're feeling crazy, running ext2
  on top of it. If you're not using the ADS bootloader, you're
  welcome to blast over the mtd1 partition also.

- 16bpp mode requires a different cable than what ships with the board.
  Contact ADS or look through the manual to wire your own. Currently,
  if you compile with 16bit mode support and switch into a lower bpp
  mode, the timing is off so the image is corrupted.  This will be
  fixed soon.

Any contribution can be sent to nico@fluxnic.net and will be greatly welcome!
Loading