From: Reinhard Meyer <u-boot@emk-elektronik.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 00/15] [REWORK AVR32/AT91] additional changes for avr32
Date: Tue, 19 Apr 2011 21:36:37 +0200 [thread overview]
Message-ID: <4DADE445.4060105@emk-elektronik.de> (raw)
In-Reply-To: <7AD13591-19D9-4A6A-BD6F-2B2959F96DE9@googlemail.com>
Dear Andreas Bie?mann,
> Am 19.04.2011 um 17:49 schrieb Reinhard Meyer:
>
>> Dear Andreas Bie?mann,
>>>> Some of the patches did not apply. What did apply is now found in u-boot-atmel/next2.
>>>>
>>>> I have no idea why they do not apply, since the AVR32 part has not changed since 110202.
>>>
>>> I can check that and will rebase on u-boot-atmel/next.
>>
>> Applied to u-boot-atmel/next.
>>
>>> BTW I personally dislike your inflationary creation of new branches. The
>>> last days I could not understand why there are that much reworkXXX
>>> branches for AT91 stuff.
>>
>> Those have a date which reflect the u-boot-arm/master they were rebased onto. I rather only
>> remove them if and when all patches have been pulled into u-boot-arm (just in case).
>
> Ok, but changes to origin/master from 20101209 in rework101209 are not included in rework101217? This would not make sense to me.
I said nothing like that.
>
>>> I hope only the one with latest timestamp is
>>> worth to work with. Isn't that reworked stuff already in next branch? Or
>>> are there some tasks not yet in next branch?
>>
>> Not all is in next, all changes I did to at9sam9260/9XE/9G20-ek and out own board (TOP9000)
>> are not yet in next, I had problems rebasing them to current u-boot-arm/master and not enough
>> time yet to fix that.
>
> Ok, I've got an at91sam9260ek here and like to get it working with current mainline (plus the reworking stuff for at91 devices). Which branch should I take? Which changes are worth to look at for 2011.06 regarding sam9260 devices or is it too late for that?
Top 2 patches in rework110202 should do the trick, once they are made to apply to current next.
best regards
Reinhard
next prev parent reply other threads:[~2011-04-19 19:36 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 15:40 [U-Boot] [PATCH 00/15] [REWORK AVR32/AT91] additional changes for avr32 Andreas Bießmann
2011-02-09 15:40 ` [U-Boot] [PATCH 01/15] avr32/config.mk: simplify PLATFORM_RELFLAGS Andreas Bießmann
2011-02-09 15:40 ` [U-Boot] [PATCH 02/15] avr32: use single linker script Andreas Bießmann
2011-02-09 15:40 ` [U-Boot] [PATCH 03/15] atngw100: fix "#define XXXX 1" Andreas Bießmann
2011-02-09 15:40 ` [U-Boot] [PATCH 04/15] atstk1002: " Andreas Bießmann
2011-02-09 15:40 ` [U-Boot] [PATCH 05/15] atstk1003: " Andreas Bießmann
2011-02-09 15:40 ` [U-Boot] [PATCH 06/15] atstk1004: " Andreas Bießmann
2011-02-09 15:40 ` [U-Boot] [PATCH 07/15] atstk1006: " Andreas Bießmann
2011-02-09 15:40 ` [U-Boot] [PATCH 08/15] favr-32-ezkit: " Andreas Bießmann
2011-02-09 15:40 ` [U-Boot] [PATCH 09/15] hammerhead: " Andreas Bießmann
2011-02-09 15:40 ` [U-Boot] [PATCH 10/15] mimc200: " Andreas Bießmann
2011-02-09 15:40 ` [U-Boot] [PATCH 11/15] atngw100: move CONFIG_SYS_TEXT_BASE to header Andreas Bießmann
2011-02-09 15:40 ` [U-Boot] [PATCH 12/15] atstk100x: " Andreas Bießmann
2011-02-09 15:40 ` [U-Boot] [PATCH 13/15] favr-32-ezkit: " Andreas Bießmann
2011-02-09 15:40 ` [U-Boot] [PATCH 14/15] mimc200: " Andreas Bießmann
2011-02-09 15:40 ` [U-Boot] [PATCH 15/15] hammerhead: " Andreas Bießmann
2011-04-13 9:06 ` [U-Boot] [PATCH 00/15] [REWORK AVR32/AT91] additional changes for avr32 Andreas Bießmann
2011-04-18 12:49 ` Reinhard Meyer
2011-04-18 13:39 ` Andreas Bießmann
2011-04-19 15:49 ` Reinhard Meyer
2011-04-19 16:44 ` Andreas Bießmann
2011-04-19 19:36 ` Reinhard Meyer [this message]
2011-04-18 14:12 ` [U-Boot] [PATCH V2 00/15] *** SUBJECT HERE *** Andreas Bießmann
2011-04-18 14:12 ` [U-Boot] [PATCH V2 01/15] avr32/config.mk: simplify PLATFORM_RELFLAGS Andreas Bießmann
2011-04-18 14:12 ` [U-Boot] [PATCH V2 02/15] avr32: use single linker script Andreas Bießmann
2011-04-18 14:12 ` [U-Boot] [PATCH V2 03/15] atngw100: fix "#define XXXX 1" Andreas Bießmann
2011-04-18 14:12 ` [U-Boot] [PATCH V2 04/15] atstk1002: " Andreas Bießmann
2011-04-18 14:12 ` [U-Boot] [PATCH V2 05/15] atstk1003: " Andreas Bießmann
2011-04-18 14:12 ` [U-Boot] [PATCH V2 06/15] atstk1004: " Andreas Bießmann
2011-04-18 14:12 ` [U-Boot] [PATCH V2 07/15] atstk1006: " Andreas Bießmann
2011-04-18 14:12 ` [U-Boot] [PATCH V2 08/15] favr-32-ezkit: " Andreas Bießmann
2011-04-18 14:12 ` [U-Boot] [PATCH V2 09/15] hammerhead: " Andreas Bießmann
2011-04-18 14:12 ` [U-Boot] [PATCH V2 10/15] mimc200: " Andreas Bießmann
2011-04-18 14:12 ` [U-Boot] [PATCH V2 11/15] atngw100: move CONFIG_SYS_TEXT_BASE to header Andreas Bießmann
2011-04-18 14:12 ` [U-Boot] [PATCH V2 12/15] atstk100x: " Andreas Bießmann
2011-04-18 14:12 ` [U-Boot] [PATCH V2 13/15] favr-32-ezkit: " Andreas Bießmann
2011-04-18 14:12 ` [U-Boot] [PATCH V2 14/15] mimc200: " Andreas Bießmann
2011-04-18 14:12 ` [U-Boot] [PATCH V2 15/15] hammerhead: " Andreas Bießmann
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=4DADE445.4060105@emk-elektronik.de \
--to=u-boot@emk-elektronik.de \
--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