From: Arnd Bergmann <arnd@arndb.de>
To: Kumar Gala <galak@gate.crashing.org>
Cc: linuxppc64-dev <linuxppc64-dev@ozlabs.org>, linuxppc-dev@ozlabs.org
Subject: Re: RFC: Rev 0.5 Booting the Linux/ppc kernel without Open Firmware
Date: Tue, 20 Dec 2005 11:18:03 +0100 [thread overview]
Message-ID: <200512201118.05404.arnd@arndb.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0512191446570.4542-100000@gate.crashing.org>
On Maandag 19 Dezember 2005 21:49, Kumar Gala wrote:
> I'm still in favor of just leaving these devices as straight platform
> devices. Unless there is something that is bus specific that each device
> on the bus conforms to I dont see any reason to create a new bus type.
How do platform devices work with module autoloading? What I'm interested
in is to have stuff like the Fedora installer or kernels with modular
drivers 'just work' because they can use the same way to load their
modules that is already used for PCI devices.
AFAICS, that requires at least two things:
- The device needs to be created when the bus is probed, i.e.
of_device_register can not be called from inside the driver
module_init() function.
- The bus type needs to create a modalias file so user space can
do the matching with the of device table in the modules.
Both of these should be a lot easier to implement with a special
bus type that creates entries in sysfs for a subset of the OF
device tree.
The alternative would be to represent all of the device tree
in /sys/devices, but IMHO that should better be part of
/sys/firmware with symlinks to the linux internal device tree
representation.
Arnd <><
next prev parent reply other threads:[~2005-12-20 10:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-05 21:06 RFC: Rev 0.5 Booting the Linux/ppc kernel without Open Firmware Jon Loeliger
2005-12-06 18:59 ` Michael Neuling
2005-12-06 20:08 ` RFC: Rev 0.5 Booting the Linux/ppc kernel without Open Firmwa re Jon Loeliger
2005-12-06 19:48 ` RFC: Rev 0.5 Booting the Linux/ppc kernel without Open Firmware Arnd Bergmann
2005-12-07 0:17 ` David Gibson
2005-12-07 16:54 ` Kumar Gala
2005-12-17 21:59 ` Benjamin Herrenschmidt
2005-12-18 6:35 ` Segher Boessenkool
2005-12-18 7:18 ` Benjamin Herrenschmidt
2005-12-19 20:49 ` Kumar Gala
2005-12-20 10:18 ` Arnd Bergmann [this message]
2005-12-20 17:26 ` Kumar Gala
2005-12-20 18:58 ` Arnd Bergmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200512201118.05404.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=galak@gate.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=linuxppc64-dev@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).