On Fri, 30 Jul 2010, David Young wrote:
On Thu, Jul 29, 2010 at 11:20:39AM +0300, Jukka Ruohonen wrote:
A small note: focusing on isa(4), legacy drivers, and their configuration
hides the real issue, which is that we need a 1:1 mapping between the normal
and the ACPI device tree. This is
On Tue, Jul 27, 2010 at 09:23:04AM +0200, Martin Husemann wrote:
On Tue, Jul 27, 2010 at 01:56:23AM +, Quentin Garnier wrote:
For free is a subjective thing. I don't think using device_register()
--which is a MD callback--to pass information between two MI drivers is
free.
Well,
On Wed, Jul 28, 2010 at 03:09:36PM +, Quentin Garnier wrote:
On Tue, Jul 27, 2010 at 09:23:04AM +0200, Martin Husemann wrote:
On Tue, Jul 27, 2010 at 01:56:23AM +, Quentin Garnier wrote:
For free is a subjective thing. I don't think using device_register()
--which is a MD
On Tue, Jul 27, 2010 at 01:56:23AM +, Quentin Garnier wrote:
For free is a subjective thing. I don't think using device_register()
--which is a MD callback--to pass information between two MI drivers is
free.
Well, using a MD callback to attach MD information from ACPI somehow
makes sense
On Mon, Jul 26, 2010 at 08:25:10AM +0300, Jukka Ruohonen wrote:
On Sun, Jul 25, 2010 at 09:22:53PM +, Quentin Garnier wrote:
bridges (mostly on x86). An even older idea of mine is to finally see
legacy devices listed in the ACPI tables attached to the PCI-ISA bridge
where they
On Sun, Jul 25, 2010 at 09:22:53PM +, Quentin Garnier wrote:
Hi all,
I'm looking for comments about what I call device flavours. The best
example of the kind of situation it tries to be an answer for is the
multiplicity of drivers one can find around the source tree for PCI-ISA
bridges
On Mon, Jul 26, 2010 at 06:27:55PM -0500, David Young wrote:
On Sun, Jul 25, 2010 at 09:22:53PM +, Quentin Garnier wrote:
Hi all,
I'm looking for comments about what I call device flavours. The best
example of the kind of situation it tries to be an answer for is the
multiplicity
Hi all,
I'm looking for comments about what I call device flavours. The best
example of the kind of situation it tries to be an answer for is the
multiplicity of drivers one can find around the source tree for PCI-ISA
bridges (mostly on x86). An even older idea of mine is to finally see
legacy
I'm looking for comments about what I call device flavours. [...]
I'm having trouble seeing what this offers over things (like scsibus)
where an abstraction attaches at real hardware and then other things
attach to the abstraction.
flavour acpiib at pci: acpinodebus
filedev/acpi/acpiib.c
On Sun, Jul 25, 2010 at 05:54:01PM -0400, der Mouse wrote:
I'm looking for comments about what I call device flavours. [...]
I'm having trouble seeing what this offers over things (like scsibus)
where an abstraction attaches at real hardware and then other things
attach to the abstraction.
On Sun, Jul 25, 2010 at 09:22:53PM +, Quentin Garnier wrote:
bridges (mostly on x86). An even older idea of mine is to finally see
legacy devices listed in the ACPI tables attached to the PCI-ISA bridge
where they logically belong, and device flavours can be used for that,
too.
I am not
11 matches
Mail list logo
