Bug#281952: additional /proc/device-tree patch for this issue. ...
Juergen Kreileder
Juergen Kreileder <jk@blackdown.de>, 281952@bugs.debian.org
Sun, 23 Jan 2005 15:06:34 +0100
Sven Luther <sven.luther@wanadoo.fr> writes:
> On Sun, Jan 23, 2005 at 01:13:01PM +0100, Juergen Kreileder wrote:
>> Hehe :-) (Using the kernel provided by Debian would mean wasting
>> 2GB of memory on my machine.)
>
> So you are using a 64bit kernel, or is there anything else in
> particular you have a problem with ?
No, I mainly use it because the 32-bit kernel only sees half of the
RAM (2 of 4 GB). (Another reason is that I want to Java working on
both PPC32 and PPC64 in the long term.)
> Mmm, indeed. The following alogirthm is a rafinement of the current
> setup in CVS :
>
> 1) if there is no /proc/device-tree/aliases/via-pmu, we quit.
> 2) if there is no /proc/device-tree/aliases/mac-io (should never be
> the case if there is a via-pmu i think), we quit too.
> 3) if there is no /proc/device-tree/`cat
> /proc/device-tree/aliases/mac-io`/backlight we quit too, since
> there is no fblevel stuff available in /dev/pmu. => obvious
> problem is if there is a backlight without via-pmu, or if the
> backlight is not on node mac-io. I doubt this happens for now,
> and we can fix those cases later if they show up.
>
> And then, we continue with the normal stuff :
>
> 4) if there is no /dev/pmu, we warn the user silently and quit.
> 5) if /dev/pmu is not writable, we warn the user silently, and quit.
> 6) if it passes upto here, we do the fblevel stuff.
> 7) we add a mention to the above in README.Debian, including an
> example on how to make /dev/pmu usable with and without
> udev. Also a warning on the security risks involved.
>
> Does this sound acceptable ?
Sounds fine to me. Thanks!
Juergen
--
Juergen Kreileder, Blackdown Java-Linux Team
http://www.blackdown.org/java-linux/java2-status/