[lkml]   [2009]   [Jun]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC/PATCH 2.6.32] Simple Firmware Interface (SFI): initial support

> > not enthusiastic about seeing this presented as a fait accompli in
> > generic driver code, rather than under arch/x86/moorestown.
> Certainly wouldn't be a real problem if it started there and migrated
> if/when it proves to be more generic.

There are no drivers in drivers/sfi/, nor will there ever be.

I followed the broken topology used by ACPI, which has both drivers
and non-driver-platform-dependent-code in drivers/acpi/.

I did propose fixing ACPI at one point, but there was no consensus
on where platform dependent non-driver code that runs on multiple
architectures should live. (eg, where to put drivers/acpi/acpica/*)

SFI is largely in the same boat. Though one could argue
that all of SFI could live under arch/x86 someplace,
though it will be accessed by more than moorestown specific code.

-Len Brown, Intel Open Source Technology Center

 \ /
  Last update: 2009-06-24 00:37    [W:0.057 / U:3.328 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site