From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] FDT driver initialization function declaration
Date: Tue, 10 Jul 2012 15:35:11 +0200 [thread overview]
Message-ID: <4FFC2F8F.3010402@monstr.eu> (raw)
In-Reply-To: <201207101500.57306.marex@denx.de>
On 07/10/2012 03:00 PM, Marek Vasut wrote:
> Dear Michal Simek,
>
>> Dear Wolfgang,
>>
>> On 07/10/2012 01:54 PM, Wolfgang Denk wrote:
>>> Dear Michal,
>>>
>>> In message<4FFC02BD.7060106@monstr.eu> you wrote:
>>>> just want to open new topic about FDT driver initialization function
>>>> declaration.
>>>>
>>>> There are some drivers which can be simple move to fdt initialization.
>>>> I have in my mind ethernet drivers and then systemace (I have ported
>>>> it).
>>>
>>> I"m not sure if it's a good idea to do this right now. Any such
>>> activities would in minimum cause a moving target for the upcoming
>>> driver model work, and most probably cause lots of conflicts on both
>>> sides.
>>>
>>> I think your plans should be co-ordinated (and probably be merged)
>>> with the DM group.
>>
>> I wasn't aware about this group. I was CC in that announcement email
>> but I missed it. :-(
>
> I believe we can meet up, have some good beer, where are you located in CZ?
Move to off topic discussion.
>
>> ok. I have signed to this ml. There are some familiar name and
>> also some czech guys. I have added u-boot-dm list to CC too.
>>
>> Can someone update me about current state of device-tree model?
>
> git clone git://git.denx.de/u-boot-marex.git -dm branch ... but the documents
> will soon see further updates. The rough outline is there thought. See
> doc/driver-model/
I have downloaded that tree.
>
> I hope the DM will be very easily possible to integrate with DT, it's done with
> that in mind. But we included a few more interesting components, like late
> probing of devices, unification of block devices and other craziness.
ok. Let me read it what have you done first.
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
next prev parent reply other threads:[~2012-07-10 13:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 10:23 [U-Boot] FDT driver initialization function declaration Michal Simek
2012-07-10 11:54 ` Wolfgang Denk
2012-07-10 12:24 ` Michal Simek
2012-07-10 13:00 ` Marek Vasut
2012-07-10 13:35 ` Michal Simek [this message]
2012-07-10 13:03 ` Wolfgang Denk
2012-07-10 13:12 ` Marek Vasut
2012-07-10 13:42 ` Michal Simek
2012-07-10 15:08 ` Marek Vasut
2012-07-11 6:16 ` Michal Simek
2012-07-11 9:52 ` Michal Simek
2012-07-12 7:10 ` [U-Boot] [U-Boot-DM] " Pavel Herrmann
2012-07-12 8:22 ` Michal Simek
2012-07-13 10:39 ` Tomas Hlavacek
2012-07-13 10:53 ` Marek Vasut
2012-07-10 13:47 ` [U-Boot] " Michal Simek
2012-07-10 15:11 ` Marek Vasut
2012-07-11 6:11 ` Michal Simek
2012-07-13 10:32 ` Marek Vasut
2012-07-10 13:05 ` Marek Vasut
2012-07-10 13:12 ` Simon Glass
2012-07-10 15:06 ` [U-Boot] [U-Boot-DM] " Marek Vasut
2012-07-10 13:46 ` [U-Boot] " Wolfgang Denk
2012-07-10 13:18 ` Simon Glass
2012-07-10 13:49 ` Michal Simek
2012-07-14 6:49 ` Simon Glass
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=4FFC2F8F.3010402@monstr.eu \
--to=monstr@monstr.eu \
--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