From: Andrey Volkov <avolkov@varma-el.com>
To: Greg KH <gregkh@suse.de>
Cc: Jamey Hicks <jamey.hicks@hp.com>,
linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: Where is place of arch independed companion chips?
Date: Mon, 01 Aug 2005 22:38:01 +0400 [thread overview]
Message-ID: <42EE6C09.3060609@varma-el.com> (raw)
In-Reply-To: <20050801181357.GA31144@suse.de>
Greg KH wrote:
> On Mon, Aug 01, 2005 at 08:29:35AM -0400, Jamey Hicks wrote:
>
>>Andrey Volkov wrote:
>>
>>
>>>Hi Greg,
>>>
>>>While I write driver for SM501 CC (which have graphics controller, USB
>>>MASTER/SLAVE, AC97, UART, SPI and VIDEO CAPTURE onboard),
>>>I bumped with next ambiguity:
>>>Where is a place of this chip's Kconfig/drivers in
>>>kernel config/drivers tree? May be create new node in drivers subtree?
>>>Or put it under graphics node (since it's main function of this CC)?
>>>
>>>AFAIK, this is not one such multifunctional monster in the world, so
>>>somebody bumped with this problem again in future.
>>>
>>>
>>>
>>
>>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.
May be better drivers/chipset?
Because "platform" imply only platform_device drivers,
but, SM501 as ex., could be connected through PCI too.
--
Regards
Andrey Volkov
next prev parent reply other threads:[~2005-08-01 18:38 UTC|newest]
Thread overview: 10+ 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-01 18:38 ` Andrey Volkov [this message]
2005-08-02 21:49 ` Richard Purdie
2005-08-03 9:09 ` [Linux-fbdev-devel] " 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=42EE6C09.3060609@varma-el.com \
--to=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