[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080506153901.GC22828@khazad-dum.debian.net>
Date: Tue, 6 May 2008 12:39:01 -0300
From: Henrique de Moraes Holschuh <hmh@....eng.br>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
Cc: Shaohua Li <shaohua.li@...el.com>, Holger Macht <hmacht@...e.de>,
linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org,
"Accardi, Kristen C" <kristen.c.accardi@...el.com>
Subject: Re: [PATCH] bay: Exit if notify handler cannot be installed
On Tue, 06 May 2008, Alan Cox wrote:
> On Tue, 6 May 2008 12:18:46 -0300
> Henrique de Moraes Holschuh <hmh@....eng.br> wrote:
> > On Tue, 06 May 2008, Shaohua Li wrote:
> > > The bay driver is duplicated with libata, I thought we should delete it.
> > > See bug http://bugzilla.kernel.org/show_bug.cgi?id=9526
> >
> > The bay driver is currently useless, BUT it should handle a lot of stuff
> > libata won't, such as bay batteries, bay floppies, and anything else in
> > a bay that is not a hard disk.
>
> The bay driver needs to become a service that hands out bay events to
> all the other drivers for that to happen.
Seems sensible. Any pointers? I wouldn't know how to do it (and
actually, right now I am busy working on rfkill for some stuff
thinkpad-acpi needs), but I could try to tack bay after rfkill, if
nobody beats me to it (hint!)
BTW: dock handling might share these issues as well.
The problem has a bit of a hard edge, though: if nobody binds to an ACPI
node that has an EJ0 subnode, bay needs to do it. But if someone wants
to, bay should give the node up, and somehow help that someone handle
the ejection stuff.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists