From: Andrey Volkov <avolkov@varma-el.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: gregkh@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [Linux-fbdev-devel] Where is place of arch independed companion chips?
Date: Sun, 31 Jul 2005 16:21:04 +0400 [thread overview]
Message-ID: <42ECC230.7070004@varma-el.com> (raw)
In-Reply-To: <42EC5659.7010300@gmail.com>
Hi Tony,
Antonino A. Daplas 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)?
>
>
> You will have to split your driver (graphics under drivers/video, usb
> under drivers/usb, ac97 under sound, video capture under drivers/media,
> etc.
Yes, it was first what I try, BUT - all these drivers have common
code (as bus driver, in my case) and some of private headers.
And problem exactly in this code. This code NOT video/audio....., this
code is abstract bus driver, and doesn't fall under some exist kernel
tree node :(.
--
Regards
Andrey Volkov
next prev parent reply other threads:[~2005-07-31 12:21 UTC|newest]
Thread overview: 15+ 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 [this message]
2005-08-01 12:29 ` Jamey Hicks
2005-08-01 18:13 ` Greg KH
2005-08-01 18:13 ` Greg KH
2005-08-01 18:38 ` Andrey Volkov
2005-08-02 21:49 ` Richard Purdie
2005-08-02 21:49 ` Richard Purdie
2005-08-03 9:09 ` Andrey Volkov
2005-08-03 9:09 ` [Linux-fbdev-devel] " Andrey Volkov
2005-08-08 21:09 ` Mark Underwood
2005-08-08 21:09 ` Mark Underwood
2005-08-03 6:17 ` Pavel Machek
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=42ECC230.7070004@varma-el.com \
--to=avolkov@varma-el.com \
--cc=gregkh@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.