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: Mon, 09 Nov 2009 19:57:28 +0100 [thread overview]
Message-ID: <4AF86618.9060400@free.fr> (raw)
In-Reply-To: <73173D32E9439E4ABB5151606C3E19E202F45D49DE@SC-VEXCH1.marvell.com>
Hi PRafulla,
Prafulla Wadaskar a ?crit :
> 1. For SOC support Orion should be implemented similar to Kirkwood
> (you agreed on this)
I still do. :)
> 2. For common drivers for (ex: kirkwood_egiga.c) the common code must
> be abstracted to egiga_core.c and architecture specific code must be
> supported through kirkwood_egiga.c/h and orion_egiga.c/h, this way it
> would make it more clean and structured.
Agreed.
> What is your opinion with #2 suggestion?
Sounds fine! I'll start submitting patches for both common drivers and
orion support based on this proposal.
Regarding the arch-specific parts of current driver code, should they
end up in cpu/arm926ejs/{kirkwood,orion5x} or stay in drivers/*? I tend
like cpu/arm926ejs/* better as it puts everything arch-specific in a
single place.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2009-11-09 18:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4AEECD8E.1080803@free.fr>
2009-11-09 16:43 ` [U-Boot] Best way of making some drivers common across kirkwood and orion5x SoCs? Prafulla Wadaskar
2009-11-09 18:57 ` Albert ARIBAUD [this message]
2009-11-10 1:54 ` Prafulla Wadaskar
2009-10-31 9:12 Albert ARIBAUD
2009-10-31 9:13 ` Albert ARIBAUD
2009-10-31 14:50 ` Wolfgang Denk
2009-10-31 15:12 ` Albert ARIBAUD
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
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=4AF86618.9060400@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 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.