From: Richard Purdie <rpurdie@rpsys.net>
To: Greg KH <gregkh@suse.de>
Cc: Jamey Hicks <jamey.hicks@hp.com>,
Andrey Volkov <avolkov@varma-el.com>,
linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: Where is place of arch independed companion chips?
Date: Tue, 02 Aug 2005 22:49:39 +0100 [thread overview]
Message-ID: <1123019379.7782.86.camel@localhost.localdomain> (raw)
In-Reply-To: <20050801181357.GA31144@suse.de>
On Mon, 2005-08-01 at 11:13 -0700, Greg KH wrote:
> > Good question. I was about to submit a patch that created
> > drivers/platform because the toplevel driver for MQ11xx is a
> > platform_device driver. Any thoughts on this?
>
> drivers/platform sounds good to me.
In another thread (about the ucb1x00) we came up with the idea of
drivers/mfd (mfd = multi function devices).
The core and platform specific parts would live here with suitable clear
naming and the subsection specific parts that were separable would live
in the appropriate place within the kernel.
Just another idea to add to the mix and removes the dilemma of a
multifunction device with isn't platform based...
Richard
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
next prev parent reply other threads:[~2005-08-02 21:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-30 11:52 Where is place of arch independed companion chips? Andrey Volkov
2005-07-31 4:40 ` [Linux-fbdev-devel] " Antonino A. Daplas
2005-07-31 12:21 ` Andrey Volkov
2005-08-01 12:29 ` Jamey Hicks
2005-08-01 18:13 ` Greg KH
2005-08-02 21:49 ` Richard Purdie [this message]
2005-08-03 9:09 ` Andrey Volkov
2005-08-08 21:09 ` Mark Underwood
2005-08-03 6:17 ` Pavel Machek
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=1123019379.7782.86.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=avolkov@varma-el.com \
--cc=gregkh@suse.de \
--cc=jamey.hicks@hp.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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).