From: David Brownell <david-b@pacbell.net>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Cc: kyle moffett <mrmacman_g4@mac.com>
Subject: Re: [PATCH] [2.6] Clean up SL811 headers
Date: Thu, 6 Jan 2005 01:31:28 -0800 [thread overview]
Message-ID: <200501060131.28421.david-b@pacbell.net> (raw)
Kyle Moffett said:
> The USB SL811 host has a structure stuck in linux/usb_sl811.h As this
> structure is kernel private and only used by a single piece of code,
That's very wrong ... the structure in question is the interface between
the board-specific setup and the driver (as it says in the comment). A
better way to put the situation is that www.kernel.org doesn't currently
bundle support for a board that wires that chip into its platform_bus.
> this patch moves it to the header file from which it is used, deleting the
> old one.
Here's a thought experiment for you ... do that for EVERY driver
on the platform_bus, and see how quickly you get a big mess.
Board support packages on 2.4 tended to take that approach;
good riddance, IMO.
When you take that approach, then adding support for a new
board means ** CHANGING EVERY DRIVER USED WITH THAT BOARD **
to know how the chip is set up on that particular board.
IRQs, addressing, CPU and GPIO pin multiplexing, support
logic ... yeech!
Better to have a single arch/XYZ/mach-ZYX/board-ABC.c file that
just sets up the relevant platform devices, and the platform_data
those drivers use. The board support packages should be small,
mostly using standard drivers ... not be invasive monsters.
- Dave
next reply other threads:[~2005-01-06 9:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-06 9:31 David Brownell [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-06 1:30 Kyle Moffett
2005-01-06 9:12 ` Russell King
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=200501060131.28421.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.com \
/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
all inboxes | Powered by JetHome®