From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] Add package raspberrypi-firmware.
Date: Sat, 20 Oct 2012 23:26:18 +0200 [thread overview]
Message-ID: <87vce4u96t.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <CA+wH294BUL_+SP55er=j9CgEf6N3VAQsrfbtjfvzywRVn2jb-Q@mail.gmail.com> (Alex Bradbury's message of "Sat, 20 Oct 2012 22:10:57 +0100")
>>>>> "Alex" == Alex Bradbury <asb@asbradbury.org> writes:
Alex> On 20 October 2012 20:49, Belisko Marek <marek.belisko@gmail.com> wrote:
>> Hi,
>>
>> just want to ask it this patch is in queue. It's month it was submitted.
Yes, sorry about that. I just started looking at the patch now.
Alex> I'd suggest it's probably not worth committing as-is, because this
Alex> weekend we finally got rid of the multiple start_*.elf files.
Ahh, interesting - So how is the memory layout then defined?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-10-20 21:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-20 20:37 [Buildroot] [PATCH v2] Add package raspberrypi-firmware Marek Belisko
2012-10-02 16:41 ` Arnout Vandecappelle
2012-10-20 19:49 ` Belisko Marek
2012-10-20 21:10 ` Alex Bradbury
2012-10-20 21:24 ` Belisko Marek
2012-10-20 21:26 ` Peter Korsgaard [this message]
2012-10-20 21:27 ` Belisko Marek
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=87vce4u96t.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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