> > Yup. I need to look at what apmd does and if it makes sense to
> > provide support for it or not, but in the meantime, there's
> > probably no need for it. That should be confirmed however.
> >
> > Ben.
>
> OK, it seems fair for me to resume my work on pmud then. I wasn't sure
> if pmud was
Benjamin Herrenschmidt wrote:
and it implements /proc/apm for battery infos, but the infos there are
That part was actually fairly easy IIRC (did that for 2.2.19).
Well, the 2400/3400/3500 is not so easy, especially without the
floats in kernel ;) I'd be glad to have some testers with these
> >MOL rsync? Do share ...
>
> rsync:
>
> rsync -vcaz zorn.theophys.kth.se::mol mol-rsync
>
> BitKeeper:
>
> bk clone bk://zorn.theophys.kth.se:5000 mol-bk
Thanks; I still see a potential problem with MMU context allocation here:
Paul's new code uses a bitmap to keep track of cont
>MOL rsync? Do share ...
rsync:
rsync -vcaz zorn.theophys.kth.se::mol mol-rsync
BitKeeper:
bk clone bk://zorn.theophys.kth.se:5000 mol-bk
> >That part was actually fairly easy IIRC (did that for 2.2.19).
>
> Well, the 2400/3400/3500 is not so easy, especially without the
> floats in kernel ;) I'd be glad to have some testers with these
Yep, that gave me a headache for a while as well (that code was never
tested on 3400 etc though,
>
>> and it implements /proc/apm for battery infos, but the infos there are
>
>That part was actually fairly easy IIRC (did that for 2.2.19).
Well, the 2400/3400/3500 is not so easy, especially without the
floats in kernel ;) I'd be glad to have some testers with these
machines to tell me if /proc
6 matches
Mail list logo
