Re: X on Mac

2007-05-30 Thread Michael Schmitz
> > whoops, looks you guys beat me to it. both finn's 20 and christians 21
> > have
> >
> > CONFIG_MAC_ADBKEYCODES=y
>
> That's because I used the debian config for that kernel. I build smaller
> kernels for myself, and I don't enable CONFIG_MAC_ADBKEYCODES. It doesn't
> do anything in 2.6.x. It should be removed from Kconfig.

It used to work until about 2.6.14 or shortly before that; I kept my
powermac at ADB keycodes for a long time because Linux keycode was utterly
broken.

> > i should try booting with kernel option keyboard_sends_linux_keycodes=1
>
> The 2.6.x kernel doesn't use that either (I don't know if userspace does
> anything with it).

That kernel option (or sysctl key) switched to Linux keycodes if ADB
keycodes were compiled in. Testing the proc file
/proc/sys/mac_hid/keyboard_sends_linux_keycodes was the only way to figure
out what kind of keycodes were used, and set the console maps accordingly.

Michael


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: X on Mac

2007-05-30 Thread Finn Thain


On Wed, 30 May 2007, Michael Schmitz wrote:

> > > whoops, looks you guys beat me to it. both finn's 20 and christians 
> > > 21 have
> > >
> > > CONFIG_MAC_ADBKEYCODES=y
> >
> > That's because I used the debian config for that kernel. I build 
> > smaller kernels for myself, and I don't enable CONFIG_MAC_ADBKEYCODES. 
> > It doesn't do anything in 2.6.x. It should be removed from Kconfig.
> 
> It used to work until about 2.6.14 or shortly before that; I kept my 
> powermac at ADB keycodes for a long time because Linux keycode was 
> utterly broken.

The mainline seems to have dropped that stuff prior to 2.6.0 (other than 
what's left in Kconfig). I wonder if debian kernels (still) add it back 
in?

-f


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: X on Mac

2007-05-30 Thread Brian Morris

On 5/29/07, Finn Thain <[EMAIL PROTECTED]> wrote:



On Tue, 29 May 2007, Brian Morris wrote:

> On 5/27/07, Finn Thain <[EMAIL PROTECTED]> wrote:
> >
> >
> > On Sat, 26 May 2007, Joel Ewy wrote:
> >
> > > Hmm.  As I recall, there is another layout (or was in XFree86 4.x)
> > > for the Mac called something like "macintosh_old".  I believe this
> > > was for the older, small ADB keyboards that didn't have Function
> > > keys.  It sounds like you're using a full-sized keyboard, but it
> > > might tell us something if you try out the other layout.
> >
> > I think macintosh_old is for old kernels (or newer kernels that have
> > been configured to send ADB keycodes -- but I've never seen one, since
> > powerpc and m68k switched to linux keycodes years ago).
>
> actually, no, we just switched.

Sure you just switched, but others have been running 2.6 on m68k macs for
years.

certainly not anywhere near production levels. the 2.6 kernels I got from
you all have only become useable in the last six months. and only really
useable since your last patch, that was not to hang my q630 at shutdown.
(thanks).

i do realize though that it takes years to develop the kernels and you
all kernel
hackers have been working hard for a while. despite all that there has to be
a reasonably useably system that people are willing to upgrade to, that
most of the users of sarge would. it could be that almost now.

I have been a half time unix admin in the past and it was something of a testing
research environment where my own career had eventually suffered to the
point where i had to give it up. My point is that although I am willing to help
up to a point, that is, I hope that others can/will pick up the new system too.
Particularly people who are interested in applications which can be conservative
in their use of resources (or application environments).

I think of quadra as sort of a baseline. we had sun and next machines going
well that were useful (actually the web was born in December 1990 on
the next) in the early 90s that were about as modern as we see today.
Although it
seems amazing that these old macs work, actually it is reasonable that
they should, it is the new machines that as actually supercomputers are
underperforming (in some ways).


AFAIK, ADB keycodes were deprecated around 2.4 by those Debian packages
that care about the console. And for ADB, naturally m68k follows in the
powermac footsteps.


So, you think that the X keyboard and the console are completely unconnected ?

I thought about put back the old mac consolekeymap. I could start X
from ssh login and see if the old mac X keymap then works.




> whoops, looks you guys beat me to it. both finn's 20 and christians 21
> have
>
> CONFIG_MAC_ADBKEYCODES=y

That's because I used the debian config for that kernel. I build smaller
kernels for myself, and I don't enable CONFIG_MAC_ADBKEYCODES. It doesn't
do anything in 2.6.x. It should be removed from Kconfig.

> i should try booting with kernel option keyboard_sends_linux_keycodes=1

The 2.6.x kernel doesn't use that either (I don't know if userspace does
anything with it).


well heres another puzzle:

there is a support script in /usr/share/console which is supposed to
pick the good console keymap. however for 68k it needs to read
Model: Macintosh
out of /proc/hardware, which exists but is empty. there fore I assume
that debconf or whatever installation / upgrade / reinstallation will not
pick the keymap correctly. since /proc is not regular file you cannot change
its contents, unless you know how it is set up ( I don't) ?




-f



Brian

-- Its been true for twenty years - you can pretty much live in emacs --


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]



Re: X on Mac

2007-05-30 Thread Finn Thain


On Wed, 30 May 2007, Brian Morris wrote:

> So, you think that the X keyboard and the console are completely 
> unconnected ?

If I run loadkeys on my (x86) laptop, virtual consoles are affected but 
xorg is not. And I gather that the ADB->linux keycode mapping happens 
lower in the input layers where it affects both. But, someone who 
understands the HID code would better answer your question.

> well heres another puzzle:
> 
> there is a support script in /usr/share/console which is supposed to
> pick the good console keymap. however for 68k it needs to read
> Model: Macintosh
> out of /proc/hardware, which exists but is empty.

Odd. Which machine/kernel is that? This from a test I did a while back:

$ cat /proc/hardware
Model:  Macintosh IIx
System Memory:  8192K
$ cat /proc/version
Linux version 2.6.19.1-m68k ([EMAIL PROTECTED]) (gcc version 3.3.6) #12 Thu Jan 
11 16:35:44 EST 2007

> there fore I assume that debconf or whatever installation / upgrade / 
> reinstallation will not pick the keymap correctly. since /proc is not 
> regular file you cannot change its contents, unless you know how it is 
> set up ( I don't) ?

I don't get it. The consoles on my macs work without loading any keymap at 
all. And what can you infer about the keymap from "Macintosh" anyway? Even 
powerbooks are going to say "Macintosh Powerbook" in /proc/hardware.

-f


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]