From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] Best way of making some drivers common across kirkwood and orion5x SoCs?
Date: Sat, 31 Oct 2009 16:12:27 +0100 [thread overview]
Message-ID: <4AEC53DB.6050509@free.fr> (raw)
In-Reply-To: <20091031145030.8B687C88C7@gemini.denx.de>
Wolfgang Denk a ?crit :
> "soc.h" is eventually a too generic name.
I'd actually chosen it "as generic as" the 'cpu.h' file which already
exists in the kirkwood arch (and others), but making it more specific is
ok, as long as it is not as specific as 'kirkwood' -- see below for an
alternate proposal.
> Please don't use symlinks.
I've already started with replacing the file rather than symlinking, so
that's fine with me.
>> Would this approach be clean enough to be considered for inclusion
in mainline?
>
> Yes, except for the "soc.h" name. And no links, please.
Would a name such as "marvell.h" be more acceptable? This would be
consistent with my intent to replace kirkwood references with marvell
ones in all non-kirkwood-specific symbols, e.g. kikwood_egiga_initialize
would become marvell_egiga_initialize etc.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2009-10-31 15:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-31 9:12 [U-Boot] Best way of making some drivers common across kirkwood and orion5x SoCs? Albert ARIBAUD
2009-10-31 9:13 ` Albert ARIBAUD
2009-10-31 14:50 ` Wolfgang Denk
2009-10-31 15:12 ` Albert ARIBAUD [this message]
2009-10-31 15:23 ` Wolfgang Denk
2009-11-01 1:00 ` Albert ARIBAUD
2009-11-02 8:42 ` Prafulla Wadaskar
2009-11-02 10:04 ` Albert ARIBAUD
2009-11-02 11:29 ` Prafulla Wadaskar
2009-11-02 14:26 ` Albert ARIBAUD
2009-11-02 8:41 ` Prafulla Wadaskar
2009-11-01 6:12 ` Prafulla Wadaskar
[not found] <4AEECD8E.1080803@free.fr>
2009-11-09 16:43 ` Prafulla Wadaskar
2009-11-09 18:57 ` Albert ARIBAUD
2009-11-10 1:54 ` Prafulla Wadaskar
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=4AEC53DB.6050509@free.fr \
--to=albert.aribaud@free.fr \
--cc=u-boot@lists.denx.de \
/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