			   ARM Linux 2.1.99
			   ================

  Since this is a development kernel, it will not be as stable as the 2.0
  series, and can cause very nasty problems (eg, trashing your hard disk).
  When running one of these kernels, I advise you to back up the complete
  contents of all your hard disks.

  ϳȯΥͥǤΤǡʥС2.0 ꡼ۤɰꤷư
  ʤǤ礦ʤΥϡɥǥ򥰥㥰ˤ褦
  ⤷ޤ󡣥ͥѤݤˤϡϡǥΤ
  ƤƤХååפƤȤ򤪴ᤷޤ

Contributors
------------

׸(Contributors)  
--------------------

  Here is a list of people actively working on the project (If you
  wish to be added to the list, please email me):

  ΥץȤ濴ŪʿʪϡʲΣͤǤ

  Name: Russell King
  Mail: linux@arm.uk.linux.org
  Desc: Original developer of ARM Linux, project co-ordinator.

  Name: Russell King
  Mail: linux@arm.uk.linux.org
  Desc: ARM Linux θԡץȤζĴ

  Name: Dave Gilbert
  Mail: linux@treblig.org
  Desc: A3/4/5xx floppy and hard disk code maintainer.

  Name: Dave Gilbert
  Mail: linux@treblig.org
  Desc: A3/4/5xx եåԡȥϡɥǥΥɤΥƥʡ

  Name: Philip Blundell
  Mail: Philip.Blundell@pobox.com
  Desc: Architecture and processor selection during make config.

  Name: Philip Blundell
  Mail: Philip.Blundell@pobox.com
  Desc: make config Υƥ㡼ȥץåԤä

Todo list
---------

  This is the list of changes to be done (roughly prioritised):

  * fully test new MEMC translation code
  * fully test new AcornSCSI driver.
  * reply to email ;)

ϺȤʤФʤʪΥꥹȤǤʤäѤͥˡ

  *  MEMC Ѵɤδʥƥ
  *  AcornSCSI ɥ饤Сδʥƥ
  * email ˤֻ ;)

  
			     Notes
			     =====

Compilation of kernel
---------------------

ͥΥѥ
--------------------

  In order to compile ARM Linux, you will need a compiler capable of
  generating ARM ELF code with GNU extensions.  GCC-2.7.2.2 is good.

  ARM Linux 򥳥ѥ뤹뤿ˤϡGNU extensions Ѥ ARM ELF 
  ɤǤ륳ѥ顼ɬפˤʤޤGCC-2.7.2.2 ɤǤ礦

  To build ARM Linux natively, you shouldn't have to alter the ARCH = line in
  the top level Makefile.  However, if you don't have the ARM Linux ELF tools
  installed as default, then you should change the CROSS_COMPILE line as
  detailed below.

  ARM Linux ľ(natively)뤿 MakefileΤϤˤ 
  ARCH = line ѹɬפ̵ϤǤ
  
  If you wish to cross-compile, then alter the following lines in the top
  level make file:

  ѥԤСmake եμιԤѹƤ
  
  
    ARCH = <whatever>
	with
    ARCH = arm

	and

    CROSS_COMPILE=
	to
    CROSS_COMPILE=<your-path-to-your-compiler-without-gcc>
	eg.
    CROSS_COMPILE=/usr/bin/arm-unknown-linuxelf-


    ARCH = <> ιԤ ARCH = arm

	줫

    CROSS_COMPILE=
	򤳤Τ褦
    CROSS_COMPILE=<ѥ顼ؤΥѥgccϻꤷʤ>
	㤨С
    CROSS_COMPILE=/usr/bin/arm-unknown-linuxelf-

  Do a 'make config', followed by 'make dep', and finally 'make all' to
  build the kernel (vmlinux).  A compressed image can be built by doing
  a 'make zImage' instead of 'make all'.

  ͥ(vmlinux)뤿ˡ'make config', 'make dep',
  'make all'¹ԤƤ

Bug reports etc
---------------

ХݡȤʤ
----------------

  Please send patches, bug reports and code for the ARM Linux project
  to linux@arm.uk.linux.org.  Patches will not be included into future
  kernels unless they come to me (or the relevant person concerned).

  ѥåХݡȡARM Linux ץȤؤΥɤʤɤϡ
  linux@arm.uk.linux.org ޤäƤѥåϻμ긵ʤޤϴ
  ԡˤϤޤǤϥͥˤϴޤޤʤǤ礦

  When sending bug reports, please ensure that they contain all relevant
  information, eg. the kernel messages that were printed before/during
  the problem, what you were doing, etc.

  ХݡȤȤϡط뤹٤Ƥξ褦ˤƤ
  㤨С꤬ȯȯΥͥΥå䡢
  ʤ򤷤Ƥ꤬ȯʤɤǤ

  For patches, please include some explanation as to what the patch does
  and why (if relevant).

  ѥå˴ؤƤϤΥѥå򤷤ơޤʤɬפʤ⤷ط
  ʤˤȤޤ褦ˤƤ

Modules
-------

⥸塼
----------

  Although modularisation is supported (and required for the FP emulator),
  each module on an arm2/arm250/arm3 machine when is loaded will take
  memory up to the next 32k boundary due to the size of the pages.  Hence is
  modularisation on these machines really worth it?

  ⥸塼벽ϥݡȤƤޤ(FP ߥ졼Ȥɬ)
  arm2/arm250/arm3 ޥγƥ⥸塼ϥڡ¤ˤꡢ
  ɻˡ32k ñ̤ǥѡʳݡˤޤǤ顢Υ
  ǥ⥸塼벽뤳Ȥ˰̣ΤǤ礦͡

  However, arm6 and up machines allow modules to take multiples of 4k, and
  as such Acorn RiscPCs and other architectures using these processors can
  make good use of modularisation.

  Ǥ arm6 ʹߤΥޥΥ⥸塼Ǥ 4k ñ̤ǡʥ˻Ѥ
  褦ˤǤޤΤǡAcorn RiscPC 䤳ΥץåѤƤ¾
  ƥ㡼Ǥϥ⥸塼벽ԤȤǡʥΡ̵̤ʤ
  ȤǤޤ

ADFS Image files
----------------

ADFS ᡼ե
---------------------

  You can access image files on your ADFS partitions by mounting the ADFS
  partition, and then using the loopback device driver.  You must have
  losetup installed.

  ADFS ѡƥˤ륤᡼եϡADFS ѡƥ
  Ȥơ롼ץХåǥХɥ饤ФѤ뤳Ȥǥ뤳
  ȤǤޤ
  
  Please note that the PCEmulator DOS partitions have a partition table at
  the start, and as such, you will have to give '-o offset' to losetup.

  PC ߥ졼 DOS ѡƥǤϥѡƥơ֥뤬Ƭ
  ޤΤǡ losetup  "-o offset" ץꤹɬפǤ礦


Kernel initialisation abort codes
---------------------------------

ͥԻΥ
------------------------------

  When the kernel is unable to boot, it will if possible display a colour
  at the top of the screen.  The colours have the following significance
  when run in a 16 colour mode with the default palette:

    Stripes of White,Red,Yellow,Green:
       Kernel does not support the processor architecture detected.

  ͥ뤬֡Ȥ˼ԤȤˤϡǽǤв̤ξ˿ɽ
  ޤǥեȤΥѥåȤ 16⡼ɤǲƯƤ硢ϼ
  ̣ɽƤޤ

    ֡ФΥȥ饤ס
	   ͥϸФץåƥ㡼򥵥ݡȤƤ
	   

Request to developers
---------------------

ȯԤؤΥꥯ
--------------------

  When writing device drivers which include a separate assembler file, please
  include it in with the C file, and not the arch/arm/lib directory.  This
  allows the driver to be compiled as a loadable module without requiring
  half the code to be compiled into the kernel image.

  ֥ǽ񤫤줿ե򥤥󥯥롼ɤǥХɥ饤Ф
  񤯾硢arch/arm/lib ǥ쥯ȥˤǤϤʤC Υե
  ޤ褦ˤƤ뤳Ȥˤäơɥ饤С֥
  ⥸塼ˤݤ˥ɤȾʬĤޤꥢ֥ or Cʬ
  򥫡ͥΥ᡼˴ޤꤷʤǺѤߤޤ顣

  In general, try to avoid using assembler unless it is really necessary.  It
  makes drivers far less easy to port to other hardware.

  ɬפʾơ֥Ѥ뤳Ȥ򤱤褦
  ƤΥɥ饤С¾Υϡɥ˥ݡƥ󥰡ʰܿ
  뤳ȤˤʤäƤޤޤ顣

ST506 hard drives
-----------------

ST506 ϡɥɥ饤
--------------------

  The ST506 hard drive controllers seem to be working fine (if a little
  slowly).  At the moment they will only work off the controllers on an
  A4x0's motherboard, but for it to work off a Podule just requires
  someone with a podule to add the addresses for the IRQ mask and the
  HDC base to the source.

  ST506 ϡɥǥɥ饤֡ȥϡä٤ɤޤ
  ʤưƤޤȯԤϡA4x0 ϤΥޥܡɤǺⳫȯ
  ʤȻפޤ⤷ΥޥܡɤʤСݥ塼ä
  ͤ椺Ƴȯʤ뤷ʤǤǥȥ 
  IRQ ѹ뤿ΥޥȥȥΥɥ쥹򥫡ͥ륽˵
  ҤƳȯʤޤ礦

  As of 31/3/96 it works with two drives (you should get the ADFS
  *configure harddrive set to 2). I've got an internal 20MB and a great
  big external 5.25" FH 64MB drive (who could ever want more :-) ).

  1996ǯ331顢ɥ饤 2 ĤǤư褦ˤʤޤ
  ADFS *configure harddrive  2 ˥åȤɬפǤ礦ˡ
   20MB ¢Ѥȡ5.25"  FH 64MB ɥ饤֤ꤷޤʤä
  礭ΤߤͤʤƤǤ礦 :-)ˡ
  FH  եϥȤǤ

  I've just got 240K/s off it (a dd with bs=128k); thats about half of what
  RiscOS gets; but it's a heck of a lot better than the 50K/s I was getting
  last week :-)

  240K/s ®٤Фޤdd ޥ bs=128kǡ;  RiscOs 
  Ф®٤ȾʬǤ轵 50K/s ʤƤ®٤٤
  ʤޥǤ :-)
  
  Known bug: Drive data errors can cause a hang; including cases where
  the controller has fixed the error using ECC. (Possibly ONLY
  in that case...hmm).

  Known Хɥ饤֥ǡ顼ȥϥ󥰥åפ뤫
  ޤ㤨Хȥ餬 ECC ǥ顼Ԥä
  ʤɤǤʤ֤󡢤ΥȻפޤɡˡ

1772 Floppy
-----------
  This also seems to work OK, but hasn't been stressed much lately.  It
  hasn't got any code for disc change detection in there at the moment which
  could be a bit of a problem!  Suggestions on the correct way to do this
  are welcome.

  ưƤ褦ǤǤߤǤϤޤܤƤ
  󡣺ΤȤǥ򴹤줿Ȥ򸡽Ф٤νʬʥɤ
  ޤ󤫤顢꤬뤫Τޤ ˡư˴
  ƤϤĤǤⴿޤޤ

Kernel entry (head-armv.S)
--------------------------
  The initial entry into the kernel made via head-armv.S uses architecture
  independent code.  The architecture is selected by the value of 'r1' on
  entry, which must be kept unique.  You can register a new architecture
  by mailing the following details to rmk@arm.uk.linux.org.  Please give
  the mail a subject of 'Register new architecture':

  head-armv.s ͳǥͥꤵ줿ȥ꡼ϥƥ㡼
  ¸ΥɤѤƤޤƥϥȥ꡼ 'r1' 
  ͤˤä򤵤ޤοͤϥˡɬפޤξܺ٤ 
  rmk@arm.uk.linux.org ˥᡼뤹뤳Ȥˤäơƥ
  Ͽ뤳ȤǤޤ᡼ subject  'Register new architecture' 
  褦ˤƤ

    Name: <name of your architecture>
    ARCHDIR: <name of include/asm-arm/arch-* directory>
    Description:
    <description of your architecture>

    Name: <ƥ̾>
    ARCHDIR: <include/asm-arm/arch-* ǥ쥯ȥ̾>
    Description:
    <ƥ>

  Please follow this format - it is an automated system.  You should
  receive a reply the next day.

  ΥեޥåȤ˽äƤ  ưƤޤ顣ˤ
  ֻ(reply)ϤǤ
  
---
Russell King (03/05/1998)

ܸ  (1999/04/16)
