From: Antony Pavlov <antonynpavlov@gmail.com>
To: Shinya Kuribayashi <skuribay@pobox.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 1/4] Add MIPS arch support to barebox
Date: Mon, 4 Jul 2011 00:40:10 +0400 [thread overview]
Message-ID: <CAA4bVAGP3L_MgNu8-SVjAdX2badmFrfjzfs48ZyUBg2n9yJ=uw@mail.gmail.com> (raw)
In-Reply-To: <4E0F2158.4050505@pobox.com>
On 2 July 2011 17:47, Shinya Kuribayashi <skuribay@pobox.com> wrote:
> On 6/29/11 12:24 PM, Antony Pavlov wrote:
>>
>> Barebox can use only uncached memory.
>
> In addition to super-summarized one-liner commit log, I'd like to see
> the reason why it is.
Because the using of KSEG1 is most elementary way to make barebox work on MIPS.
If you use KSEG1 you have no code for cache setup and no cache exceptions.
> Is there any reason why head.S, not start.S? Other archs in the tree
> name it start*.[cS].
x86 and sandbox use other names.
In mips linux this file have name head.S.
But I don't insist on this name.
>> arch/mips/include/asm/barebox.h | 24 +
>> arch/mips/include/asm/bitops.h | 32 ++
...
>> arch/mips/include/asm/swab.h | 59 ++
>> arch/mips/include/asm/types.h | 44 ++
>> arch/mips/include/mach/debug_ll.h | 35 ++
>
> And I would like to know where these kernel headers from. If it's the
> Linux kernel, which version they're based on, and what modifications are
> made for barebox. Such information is useful when we add/remove bits in
> the future. This is why I did for my patches in this regard in a careful
> manner.
Good idea! I will use it.
> If it's from U-Boot tree,it's bad idea and let's redo from the scratch.
> Starting small is good, starting based on U-Boot is not good in any area.
:))))
is U-Boot so terrible?
But I agree, now there is no reason starting based on U-Boot.
--
Best regards,
Antony Pavlov
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2011-07-03 20:40 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 3:24 Antony Pavlov
2011-06-29 3:24 ` [PATCH 2/4] MIPS: add Malta machine " Antony Pavlov
2011-06-30 3:02 ` Jean-Christophe PLAGNIOL-VILLARD
2011-07-02 14:41 ` Shinya Kuribayashi
2011-07-02 16:45 ` Jean-Christophe PLAGNIOL-VILLARD
2011-07-03 20:44 ` Antony Pavlov
2011-07-04 5:11 ` Jean-Christophe PLAGNIOL-VILLARD
2011-07-04 8:54 ` Antony Pavlov
2011-07-04 8:52 ` Jean-Christophe PLAGNIOL-VILLARD
2011-07-03 20:50 ` Antony Pavlov
2011-06-29 3:24 ` [PATCH 3/4] MIPS: add qemu malta board " Antony Pavlov
2011-06-30 2:58 ` Jean-Christophe PLAGNIOL-VILLARD
2011-06-30 9:12 ` Antony Pavlov
2011-06-30 9:38 ` Jean-Christophe PLAGNIOL-VILLARD
2011-06-30 10:34 ` Antony Pavlov
2011-06-29 3:24 ` [PATCH 4/4] MISP: add documentation template Antony Pavlov
2011-06-29 5:40 ` [PATCH 1/4] Add MIPS arch support to barebox Jean-Christophe PLAGNIOL-VILLARD
2011-06-29 7:53 ` Antony Pavlov
2011-06-30 2:52 ` Jean-Christophe PLAGNIOL-VILLARD
2011-06-30 7:12 ` Franck JULLIEN
2011-06-30 9:18 ` Jean-Christophe PLAGNIOL-VILLARD
2011-06-30 9:13 ` Antony Pavlov
2011-07-02 13:47 ` Shinya Kuribayashi
2011-07-02 16:46 ` Jean-Christophe PLAGNIOL-VILLARD
2011-07-03 20:40 ` Antony Pavlov [this message]
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='CAA4bVAGP3L_MgNu8-SVjAdX2badmFrfjzfs48ZyUBg2n9yJ=uw@mail.gmail.com' \
--to=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=skuribay@pobox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox