On Tue, Apr 03, 2001 at 10:35:33PM +0100, Philip Blundell wrote:
> >* this seems to imply that the ARM port needs to distinguish between
> >sub-archs, just as ppc and 68k
>
> Yes. As far as keyboard maps are concerned, there are only two flavours:
> most
> ARM machines use PC keyboards, but a few use this "acorn" mapping. You
> detect
> them by the `Hardware' field in /proc/cpuinfo; it looks like this:
>
> Processor : Intel StrongARM-110 rev 4 (v4l)
> BogoMIPS : 214.63
> Hardware : Chalice-CATS
>
> The machines that need the "acorn" keymap will have Hardware: Acorn-RiscPC,
> Acorn-A5000 or Acorn-Archimedes. The others that are supported by Debian,
> which need the PC keymap, are Chalice-CATS and Rebel-NetWinder.
I'll only distinguish the special case of these machines needing
keymap translation, against the others: they will be 'arm/riscpc', and
the other ones will stay as 'arm':
if ($arch eq 'arm') {
my $subarch;
my $isRiscPc = (system ("grep", "^Hardware *: Acorn-", "/proc/cpuinfo") ==
0);
$arch = 'arm/riscpc' if $isRiscPc;
}
> >A detailed description of the keymap will be necessary anyway; see
> >/usr/share/debhelper/dh-consoledata/templates/keymaps for the
> >definition of the console-data/keymap/* questions.
>
> I don't personally have any information beyond what's in the kmap file. I've
> asked on the debian-arm mailing list to see if there are any volunteers to
> provide the details.
I still don't have a good description of this keymap, sent to me as
"acorn/ps2.uk", which I'll include as "riscpc/riscpc-uk.kmap" unless
someone objects.
Should it really be "acorn" and not "riscpc" ? I may be intoducing
confusion here...
--
Yann Dirson <[EMAIL PROTECTED]> | Why make M$-Bill richer & richer ?
debian-email: <[EMAIL PROTECTED]> | Support Debian GNU/Linux:
| Cheaper, more Powerful, more Stable !
http://ydirson.free.fr/ | Check <http://www.debian.org/>
