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 00:20:21 +0100 [thread overview]
Message-ID: <012b01c74ca1$8ee35fe0$01c4af0a@Glamdring> (raw)
In-Reply-To: 1defaf580702091458p564ba747qc235ebe3601df497@mail.gmail.com
>> I still would like to have the complete sam926x patch set
>> implemented before we start to "play" with it
>
> Yeah, but I still think some preparatory patches are a good thing in
> order to make things easier later on.
I only see two things as a result of those prepatory patches.
1) Bugs
2) Delays in availability
I am not questioning anything you want to do, just the timing.
If we follow your recommendation you will have a bunch
of untested board patches in the mainstream u-boot,
for the sam926x.
I do not have the time to thoroughly test any changes
you do (I dont even have an at91sam9263 board).
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.
The number of users far outweisghs the number of implementers
and I think that we need to look at it from their point of view.
We are not introducing any new interfaces here,
just using the existing interfaces.
This means that it will not be harder to do any modifications
*after* the sam926x patches are applied.
It will be easier since you have better overview.
The only alternative I can see is that you take over
the responsibility for both AVR32 and AT91 U-boot
and test all modifications on all boards before submission
- Still with availability of working solution as the highest priority.
>
> Haavard
Best Regards
Ulf Samuelsson
next prev parent reply other threads:[~2007-02-09 23:20 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 [this message]
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
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='012b01c74ca1$8ee35fe0$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