From: Ulf Samuelsson <ulf@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] AT91 NAND om AT91SAM9260EK
Date: Sat, 10 Feb 2007 10:05:43 +0100 [thread overview]
Message-ID: <002201c74cf2$ef000120$01c4af0a@Glamdring> (raw)
In-Reply-To: 20070210011857.4974635265F@atlas.denx.de
> In message <012b01c74ca1$8ee35fe0$01c4af0a@Glamdring> you wrote:
>>
>> If we go my way, then we should be able to have *tested* sam926x
>> support inside U-boot very soon, and while this results
>> in duplication of a small part of the spi code on the source level
>> (no addition to the binary) I believe that
>> the benefit to the community of at91sam926x users
>> of having native support in U-Boot outweighs this duplication a lot.
>
> And once it's in, who guarantees to clean it up later? And when?
>
>> We are not introducing any new interfaces here,
>
> But we're adding to the mess of duplicated code.
>
No, that is wrong.
today at45.c is in itself a duplication.
board/at91rm9200dk/at45.c
and
board/cmc_pu2/at45.c
are duplicates (except for a bug which is not fixed in cmc_pu2)
Customers which build their own board
add additional at45.c's in their board directory.
After the patch you have a single at45.c which is common
for all at91rm9200 boards and a single spi.c which is common
for all at91rm9200 boards and an spi.c which is common for
all at91sam926x boards.
spi.c is CPU specific and the only reason you can have a single
file for the sam926x (three chips supported by that the file) contains
ifdefs
to select which chip.
Duplication is therefore reduced by the patch.
I am sure that you realize this if you get into the details.
> Best regards,
>
> Wolfgang Denk
>
Best Regards
Ulf Samuelsson ulf at atmel.com
Atmel Nordic AB
Mail: Box 2033, 174 02 Sundbyberg, Sweden
Visit: Kavalleriv?gen 24, 174 58 Sundbyberg, Sweden
Phone +46 (8) 441 54 22 Fax +46 (8) 441 54 29
GSM +46 (706) 22 44 57
Technical support when I am not available:
AT89 C51 Applications Group: mailto:micro.hotline at nto.atmel.com
AT90 AVR Applications Group: mailto:avr at atmel.com
AT91 ARM Applications Group: mailto:at91support at atmel.com
FPSLIC Application Group: mailto:fpslic at atmel.com Best AVR
link: www.avrfreaks.net
next prev parent reply other threads:[~2007-02-10 9:05 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c88e466f0702050752t16c18251gcddf40a7ec95469@mail.gmail.com>
2007-02-07 23:17 ` [U-Boot-Users] AT91 NAND om AT91SAM9260EK Ulf Samuelsson
2007-02-08 6:06 ` Stefan Roese
2007-02-08 8:34 ` Michel Benoit
2007-02-08 19:25 ` Ulf Samuelsson
2007-02-08 20:58 ` Haavard Skinnemoen
2007-02-08 22:20 ` Ulf Samuelsson
2007-02-09 15:45 ` Haavard Skinnemoen
2007-02-09 19:11 ` Ulf Samuelsson
2007-02-09 19:54 ` Haavard Skinnemoen
2007-02-09 19:39 ` Wolfgang Denk
2007-02-09 22:18 ` Ulf Samuelsson
2007-02-09 22:58 ` Haavard Skinnemoen
2007-02-09 23:20 ` Ulf Samuelsson
2007-02-09 23:42 ` Haavard Skinnemoen
2007-02-10 0:10 ` Ulf Samuelsson
2007-02-10 1:18 ` Wolfgang Denk
2007-02-10 9:05 ` Ulf Samuelsson [this message]
2007-02-10 7:23 ` Stefan Roese
2007-02-10 1:15 ` Wolfgang Denk
2007-02-10 7:32 ` Stefan Roese
2007-02-10 9:29 ` Ulf Samuelsson
2007-02-10 1:53 ` Ken Watson
[not found] <mailman.5069.1170973304.16820.u-boot-users@lists.sourceforge.net>
2007-02-08 22:57 ` Ivan Kuten
[not found] <mailman.12584.1171099992.16820.u-boot-users@lists.sourceforge.net>
2007-02-10 20:31 ` Ivan Kuten
2007-02-11 16:43 ` Ulf Samuelsson
2007-02-11 18:04 ` Haavard Skinnemoen
2007-02-11 19:42 ` Ulf Samuelsson
2007-02-11 20:23 ` Haavard Skinnemoen
2007-02-11 20:29 ` Ulf Samuelsson
2007-02-11 20:54 ` Haavard Skinnemoen
2007-02-11 21:10 ` Wolfgang Denk
2007-02-11 21:39 ` Ulf Samuelsson
2007-02-11 23:45 ` Wolfgang Denk
2007-02-12 0:26 ` Ulf Samuelsson
2007-02-12 15:18 ` Haavard Skinnemoen
2007-02-12 18:40 ` Ulf Samuelsson
2007-02-12 19:36 ` Stefan Roese
2007-02-12 19:37 ` Haavard Skinnemoen
2007-02-12 20:05 ` Ulf Samuelsson
2007-02-11 21:54 ` Ulf Samuelsson
2007-02-11 11:49 Michel Benoit
2007-02-11 16:20 ` Ulf Samuelsson
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='002201c74cf2$ef000120$01c4af0a@Glamdring' \
--to=ulf@atmel.com \
--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