From: Txema Lopez <tlopez@aotek.es>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Support for csb535fs / i.MX21 LiteKit.
Date: Thu, 01 Mar 2007 09:08:33 +0100 [thread overview]
Message-ID: <45E68A01.3060607@aotek.es> (raw)
In-Reply-To: <528646bc0702280855r83d304eo510396e5d87d9c4@mail.gmail.com>
Grant Likely wrote:
>
>
> I know that slightly modified duplicate code is common in u-boot, so
> this is not an critique on your work, but I'd really like to move away
> from this mode of operation. Duplicating the original file and
> modifying it is certainly the easiest way to add support for a new
And It makes the code more readable. It's the pro.
> 10 times and a bug is found in it at a later date; the bug fix needs
> to be applied to 10 files, not one.
Yes, It's the con. But, how many times does it happen?.
>
> Unfortunately, this situation is messy because the imx is in
> cpu/arm920t and imx32 is in cpu/arm926ejs. It probably requires the
> creation of a new directory for the common imx soc bits, but where?
> Perhaps under lib_arm/imx?
>
Ummm, lib_arm/imx?. I think this mixes up concepts.
Why not to decouple the arm cores and the SoC code?. For example:
cpu/arm/cores/arm926ejs
cpu/arm/soc/imx
Perhaps, there was a discussion about this in U-Boot and I'm talking
nonsense.
Anyway, you are the mainteiner so you have the last say. ;-)
Best regards,
Txema.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tlopez.vcf
Type: text/x-vcard
Size: 324 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20070301/4c8fb6c2/attachment.vcf
next prev parent reply other threads:[~2007-03-01 8:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 13:02 [U-Boot-Users] [PATCH] Support for csb535fs / i.MX21 LiteKit Txema Lopez
2007-02-27 17:20 ` Grant Likely
2007-02-28 7:43 ` Txema Lopez
2007-02-28 16:55 ` Grant Likely
2007-03-01 8:08 ` Txema Lopez [this message]
2007-03-01 8:17 ` Wolfgang Denk
2007-03-01 10:30 ` Txema Lopez
2007-03-01 14:23 ` Grant Likely
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=45E68A01.3060607@aotek.es \
--to=tlopez@aotek.es \
--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