From: Shinya Kuribayashi <skuribay@pobox.com>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 2/2] Add MIPS arch support to barebox
Date: Wed, 29 Jun 2011 01:23:18 +0900 [thread overview]
Message-ID: <4E09FFF6.8020603@pobox.com> (raw)
In-Reply-To: <20110628132907.GP17355@game.jcrosoft.org>
Thanks Jean for bringing up old stuff :-), and nice to see the first
(workable) MIPS port of barebox this time, Antony.
>> Is it runnable at all?
Not at all, unfortunately.
>> I think, that Shinya's concepts can be used in the future, but they
>> are very complex for initial mips support.
>>
>> IMHO, the Shinya's code is redundant (> 200K ) --- initial support
>> must be as small as possible.
I didn't care about code size, complexity, workable or not (ok, this is
important) when I was working on it. What did care about is its boot
design.Having a glance at your head.S, compute_offset part looks good.
That's a part of what I have in mind, and implemented as ADR macro in
my prototype.
I'll write a lot more some other day.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2011-06-28 16:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-27 17:13 [PATCH 1/2] include/linux/stat.h: make struct stat unified Antony Pavlov
2011-06-27 17:13 ` [PATCH 2/2] Add MIPS arch support to barebox Antony Pavlov
2011-06-28 5:11 ` Jean-Christophe PLAGNIOL-VILLARD
2011-06-28 6:14 ` Antony Pavlov
2011-06-28 9:37 ` Antony Pavlov
2011-06-28 10:06 ` Sascha Hauer
2011-06-28 13:29 ` Jean-Christophe PLAGNIOL-VILLARD
2011-06-28 16:23 ` Shinya Kuribayashi [this message]
2011-06-28 7:21 ` Sascha Hauer
2011-06-28 9:03 ` Antony Pavlov
2011-06-28 15:06 ` Shinya Kuribayashi
2011-06-28 15:42 ` Antony Pavlov
2011-06-28 6:40 ` [PATCH 1/2] include/linux/stat.h: make struct stat unified Sascha Hauer
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=4E09FFF6.8020603@pobox.com \
--to=skuribay@pobox.com \
--cc=barebox@lists.infradead.org \
--cc=plagnioj@jcrosoft.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.