Hello.
> On Thu, 04 Jul 2013 22:08:12 +0100, Stefan Schmidt wrote:
>> Hello.
>>
>> On Thu, 2013-07-04 at 11:37, Lukasz Majewski wrote:
>> > On Thu, 04 Jul 2013 17:20:34 +0800, tiger...@viatech.com.cn wrote:
>> >
>> > > Hi, experts:
>> > > I found DFU tool code had been put in drivers/dfu directory
On Thu, 04 Jul 2013 22:08:12 +0100, Stefan Schmidt wrote:
> Hello.
>
> On Thu, 2013-07-04 at 11:37, Lukasz Majewski wrote:
> > On Thu, 04 Jul 2013 17:20:34 +0800, tiger...@viatech.com.cn wrote:
> >
> > > Hi, experts:
> > > I found DFU tool code had been put in drivers/dfu directory.
> > > Previou
Hello.
On Thu, 2013-07-04 at 11:37, Lukasz Majewski wrote:
> On Thu, 04 Jul 2013 17:20:34 +0800, tiger...@viatech.com.cn wrote:
>
> > Hi, experts:
> > I found DFU tool code had been put in drivers/dfu directory.
> > Previously, it was owned by Samsung Electronics.
> >
>
> Could you be more spec
On Thu, 04 Jul 2013 17:20:34 +0800, tiger...@viatech.com.cn wrote:
> Hi, experts:
> I found DFU tool code had been put in drivers/dfu directory.
> Previously, it was owned by Samsung Electronics.
>
Could you be more specific here?
All DFU related files have following headers:
/*
* g_dnl.c --
Hi, experts:
I found DFU tool code had been put in drivers/dfu directory.
Previously, it was owned by Samsung Electronics.
Because it has been merged into uboot library.
So, it could be used or released by every ARM SOC vendor?
Best wishes,
___
U-Boot m
5 matches
Mail list logo