> > So in this example, we are exporting a number of boot devices as the
> > bios told us, so apply the rule stated above, and determine
> > if it should go into /proc or not[1].
>
> This is interesting, and I look forward to delving into the
> code. ACPI is doing something very similar. One thing I
> would like to do is create a 'platform' or 'firmware'
> top-level directory in driverfs in which all the
> various firmware drivers can display the data they ascertain from the
> firmware. Stay tuned..
Likewise, on IA-64, /proc/efi/ has EFI stuff (really only vars/ right now,
direct access to NVRAM variables), which coincidentally, I wrote, which
would benefit from a top-level 'platform' or 'firmware' directory and
migration to driverfs. Code is in arch/ia64/kernel/efivars.c. Once I nail
down the EDD code, moving efivars.c to driverfs shouldn't be hard.
> Two examples are attached:
Thanks, that helps a lot. I need to still find how to walk the list of
existing devices and gather info, for purposes of making symlinks, but I see
the existing devices that do that to use as examples.
Thanks,
Matt
-- Matt Domsch Sr. Software Engineer, Lead Engineer, Architect Dell Linux Solutions www.dell.com/linux Linux on Dell mailing lists @ http://lists.us.dell.com #1 US Linux Server provider for 2001 and Q1/2002! (IDC May 2002)- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Sep 15 2002 - 22:00:15 EST