From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
barebox@lists.infradead.org
Subject: Re: [PATCH] of: add ranges address translation for default bus
Date: Mon, 17 Jun 2013 12:23:41 +0200 [thread overview]
Message-ID: <51BEE3AD.20406@gmail.com> (raw)
In-Reply-To: <20130617074724.GK32299@pengutronix.de>
On 06/17/2013 09:47 AM, Sascha Hauer wrote:
> On Thu, Jun 13, 2013 at 08:50:30PM +0200, Sebastian Hesselbarth wrote:
>> On 06/13/13 14:48, Sascha Hauer wrote:
>>> On Thu, Jun 13, 2013 at 11:38:19AM +0200, Sebastian Hesselbarth wrote:
>>>> On 06/13/13 11:25, Sascha Hauer wrote:
>>>>> Sounds like a plan. Functions existing both in barebox and Linux should
>>>>> behave the same way. However, if Linux turns out to do something silly
>>>>> or (for our usecase) too bloated, we shouldn't do the same just because
>>>>> Linux does it.
>> pushed a branch you can have a first look at to
>>
>> git://github.com/shesselba/barebox-dove.git of-sync-v1
>
> I had a quick look at this branch. It has some really good stuff in it.
> You should post it for a closer review if you consider it ready.
Ok, I've had another round of patches in branch of-sync-part2-v1. I will
merge both and either send an RFC or merge in some clean-ups. I didn't
provide stubs for !CONFIG_OF at some places.
It is already kind of huge patch, so I prefer sending it before more
stuff gets in. Currently, it is more or less fully merged with Linux OF
API wrt base.c.
Next would be to move code that should have been in common/oftree.c in
the first place (of_add_initrd, of_print_nodes, ...), move out stuff to
of/device.c and of/address.c.
I haven't looked into barebox' driver/device backend but realized that
struct resource is attached to the device_node. Maybe it should also
move to some other struct (device_d) ?
Sebastian
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2013-06-17 10:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-12 23:09 Sebastian Hesselbarth
2013-05-19 7:34 ` Sascha Hauer
2013-05-19 8:07 ` Sebastian Hesselbarth
2013-05-19 10:39 ` Sascha Hauer
2013-05-19 10:49 ` Sebastian Hesselbarth
2013-05-19 15:20 ` Thomas Petazzoni
2013-06-11 9:33 ` Sebastian Hesselbarth
2013-06-13 9:25 ` Sascha Hauer
2013-06-13 9:38 ` Sebastian Hesselbarth
2013-06-13 12:48 ` Sascha Hauer
2013-06-13 18:50 ` Sebastian Hesselbarth
2013-06-17 7:47 ` Sascha Hauer
2013-06-17 10:23 ` Sebastian Hesselbarth [this message]
2013-06-17 10:40 ` 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=51BEE3AD.20406@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
--cc=thomas.petazzoni@free-electrons.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