From: Ulf Samuelsson <ulf@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Status of the AVR32 u-boot patches
Date: Fri, 25 Aug 2006 12:42:46 +0200 [thread overview]
Message-ID: <008501c6c834$4c1fb9c0$8d4765d5@atmel.com> (raw)
In-Reply-To: 20060825115129.528e254a@cad-250-152.norway.atmel.com
> Hi Wolfgang,
>
> I just noticed Ulf claiming that we (Atmel Norway) have submitted
> patches for AVR32 support. That is not correct as far as I know, and
> I'm the one sitting on the patches. So you can probably stop looking ;)
>
No, I have been told by someone else in Norway it happend, and this guys was obviously misinformed
I wanted to check if it was true (Notice the "is this correct" question).
> We do intend to do so, though, so the other claim that we're "ignoring
> the main U-boot tree" is not correct either. It's just that we've stuck
> to point releases so far.
More the AT91 group than you...
> Now that blackfin has "stolen" our architecture number, I guess it's
> time to get moving. Changing the architecture ID will probably break a
> lot of setups, but I guess it's better to do a clean break now, handle
> the additional support requests, and be done with it.
>
> I'll start folding and rebasing the patches against the master branch
> next week, so I'll probably have some patches ready for you in a few
> days. What's the best way to split them up? Separate patches for
> everything? Maybe I should combine the arch patch with support for one
> CPU and one board so that it's possible to actually build the result?
> I'll submit the drivers separately anyway.
>
> Ulf, I appreciate your efforts getting AVR32 support into u-boot. The
> "drivers/atmel" thing looks interesting -- have you consolidated any of
> the drivers yet?
I have put the AT91 memory drivers
* at45.c->at45dbxxx.c
* flash.c->at49bvxxx.c
* nand.c
and the dm9161a.c but since Wolfgang does not like
the idea of distributing things, I'm in between chairs at the moment.
I can send you the source files and then you can include them in your patch.
I guess it does not hurt having source available before use.
You may want to update the files, because today they configure based on different AT91 chips.
Maybe a CONFIGURE_ATMEL ??
Probably, it is a good idea to put most of the Atmel Rousset peripheral drivers in
an "board/atmel/common" directory as well.
>
> Haavard
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:[~2006-08-25 10:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-25 9:51 [U-Boot-Users] Status of the AVR32 u-boot patches Haavard Skinnemoen
2006-08-25 10:42 ` Ulf Samuelsson [this message]
2006-08-25 13:09 ` Haavard Skinnemoen
2006-08-25 17:45 ` Ulf Samuelsson
2006-08-28 11:12 ` Haavard Skinnemoen
-- strict thread matches above, loose matches on Subject: below --
2006-08-31 16:31 Ulf Samuelsson
2006-08-31 17:49 ` Haavard Skinnemoen
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='008501c6c834$4c1fb9c0$8d4765d5@atmel.com' \
--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