[U-Boot-Users] [ARM] TI DaVinci support, 2nd attempt [0/5]

[U-Boot-Users] [ARM] TI DaVinci support, 2nd attempt [0/5]

[ksi at koi8.net]

Signed-off-by: Sergey Kubushyn <ksi@koi8.net>

Here it is.

Changes:

- Split into separate board directories
- Removed changes to MTD_DEBUG (or whatever it's called)
- New CONFIG_CMD party line followed
- Some cosmetic fixes, cleanup etc.
- Patches against the latest U-Boot tree as of now.

Unfortunately it won't compile because of that BIOS emulator or what it
is...

---
******************************************************************
*  KSI at home    KOI8 Net  < >  The impossible we do immediately.  *
*  Las Vegas   NV, USA   < >  Miracles require 24-hour notice.   *
******************************************************************

[U-Boot-Users] [ARM] TI DaVinci support, 2nd attempt [0/5]

[Zach Sadecki]

 
Sergey,
  You mentioned in a previous post that you had a serial boot utility you wrote to get away from the C# one that TI has...  Did you write that in C?  Could you share it with the list, since it would be most helpful to those of us who work with Davinci boards.

Thanks for all your efforts with this port of u-boot.  It will be great to be able to move up to a clean, well written version.  I look forward to the NAND support especially, since the stuff in the TI supplied u-boot is almost 3 years old...

Zach

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20070806/79e4d2b2/attachment.htm 

[U-Boot-Users] [ARM] TI DaVinci support, 2nd attempt [0/5]

[ksi at koi8.net]

On Mon, 6 Aug 2007, Zach Sadecki wrote:

>
> Sergey,
>  You mentioned in a previous post that you had a serial boot utility
> you wrote to get away from the C# one that TI has...  Did you write that
> in C?  Could you share it with the list, since it would be most helpful
> to those of us who work with Davinci boards.

It is partially in C and partially in Assembly. I would like to share it but
it is quite messy right now, code requires a good cleanup. Unfortunately I
don't have time right now, I'm extremely busy with bringing up prototype
boards that just came in... We're very short in time so I have to get them
up and running asap and give out a list of required changes and fixes for
the final prototypes and then go into production...

So I will do it later, when that pressure is somehow lessened...

Another thing is I don't know where it belongs. Just posting it to the list
will do little good, it must go into some repository or a product. I think
it would be OK to add various bootloaders to the U-Boot tree so people would
have all the means for bringing up their hardware from totally virgin state
but that requires cooperation, willinness to add yet another tree to the
U-Boot and decision on where it should go...

> Thanks for all your efforts with this port of u-boot.  It will be great
> to be able to move up to a clean, well written version.  I look forward
> to the NAND support especially, since the stuff in the TI supplied
> u-boot is almost 3 years old...

It is not just old, it is crappy and non-working :) And their I2C stuff is
absolutely bogus...

---
******************************************************************
*  KSI at home    KOI8 Net  < >  The impossible we do immediately.  *
*  Las Vegas   NV, USA   < >  Miracles require 24-hour notice.   *
******************************************************************

[U-Boot-Users] [ARM] TI DaVinci support, 2nd attempt [0/5]

[Zach Sadecki]

It is crappy and broken...  I was just being nice :)  I'm tired of fighting problems that we would have never seen if we were using a somewhat more modern u-boot...

Thanks,
  Zach


-----Original Message-----
From: ksi@koi8.net [mailto:ksi at koi8.net]
Sent: Mon 8/6/2007 11:43 PM
To: Zach Sadecki
Cc: U-Boot list
Subject: Re: [U-Boot-Users] [ARM] TI DaVinci support, 2nd attempt [0/5]
 
On Mon, 6 Aug 2007, Zach Sadecki wrote:

>
> Sergey,
>  You mentioned in a previous post that you had a serial boot utility
> you wrote to get away from the C# one that TI has...  Did you write that
> in C?  Could you share it with the list, since it would be most helpful
> to those of us who work with Davinci boards.

It is partially in C and partially in Assembly. I would like to share it but
it is quite messy right now, code requires a good cleanup. Unfortunately I
don't have time right now, I'm extremely busy with bringing up prototype
boards that just came in... We're very short in time so I have to get them
up and running asap and give out a list of required changes and fixes for
the final prototypes and then go into production...

So I will do it later, when that pressure is somehow lessened...

Another thing is I don't know where it belongs. Just posting it to the list
will do little good, it must go into some repository or a product. I think
it would be OK to add various bootloaders to the U-Boot tree so people would
have all the means for bringing up their hardware from totally virgin state
but that requires cooperation, willinness to add yet another tree to the
U-Boot and decision on where it should go...

> Thanks for all your efforts with this port of u-boot.  It will be great
> to be able to move up to a clean, well written version.  I look forward
> to the NAND support especially, since the stuff in the TI supplied
> u-boot is almost 3 years old...

It is not just old, it is crappy and non-working :) And their I2C stuff is
absolutely bogus...

---
******************************************************************
*  KSI at home    KOI8 Net  < >  The impossible we do immediately.  *
*  Las Vegas   NV, USA   < >  Miracles require 24-hour notice.   *
******************************************************************

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.denx.de/pipermail/u-boot/attachments/20070807/94acf65d/attachment.htm 

[U-Boot-Users] [ARM] TI DaVinci support, 2nd attempt [0/5]

[Dirk Behme]

ksi at koi8.net wrote:
> Signed-off-by: Sergey Kubushyn <ksi@koi8.net>
> 
> Here it is.
> 
> Changes:
> 
> - Split into separate board directories
> - Removed changes to MTD_DEBUG (or whatever it's called)
> - New CONFIG_CMD party line followed
> - Some cosmetic fixes, cleanup etc.
> - Patches against the latest U-Boot tree as of now.

Many thanks!

> Unfortunately it won't compile because of that BIOS emulator or what it
> is...

I just sent a hackish patch to be able to at least compile.

With this, some comments to your recent patches:

1) As with your first set of patches, I can't get patch 2/5 and 4/5 
get apply cleanly. I get rejects needing manual resolve for everything 
modifying already existing files. All files/patches adding new files 
apply cleanly.

2) The net files don't compile because they need new style config option

#if defined(CONFIG_CMD_NET) ...

3) Schmoogie config needs a #undef CONFIG_CMD_EEPROM instead of a #define

4) With schmoogie config, schmoogie/dv_board.c fails linking because 
of missing forceenv(). E.g. in exports.h this is clamped by #ifdef 
CONFIG_HAS_UID. So I think misc_init_r() in all three dv_board.c need 
anything similiar.

I will send my updated versions of your patches for reference as 
answers to the individual patch mails. No, I don't want to steal 
anything. I want  to help. They resolve 1) - 3), so only (4) is open. 
Feel free to send them again with your Signed-off-by, to ignore them, 
or use them for update. You mentioned that you are short of time, so 
hopefully we can avoid to invent the wheel two times and reuse stuff 
already fixed.

For me, then everything else looks okay ;) So I think resolving (4) 
will be the hopefully final version then.

Best regards

Dirk

[U-Boot-Users] [ARM] TI DaVinci support, 2nd attempt [0/5]

[ksi at koi8.net]

On Tue, 7 Aug 2007, Dirk Behme wrote:

> ksi at koi8.net wrote:
>> Signed-off-by: Sergey Kubushyn <ksi@koi8.net>
>> 
>> Here it is.
>> 
>> Changes:
>> 
>> - Split into separate board directories
>> - Removed changes to MTD_DEBUG (or whatever it's called)
>> - New CONFIG_CMD party line followed
>> - Some cosmetic fixes, cleanup etc.
>> - Patches against the latest U-Boot tree as of now.
>
> Many thanks!
>
>> Unfortunately it won't compile because of that BIOS emulator or what
> it
>> is...
>
> I just sent a hackish patch to be able to at least compile.
>
> With this, some comments to your recent patches:
>
> 1) As with your first set of patches, I can't get patch 2/5 and 4/5 get
> apply 
> cleanly. I get rejects needing manual resolve for everything modifying 
> already existing files. All files/patches adding new files apply
> cleanly.

That is extremely strange because the entire patch is made against
yesterday's git tree. I don't know, may be you guys have some other tree,
but I made the patch against what I pulled yesterday.

> 2) The net files don't compile because they need new style config option
>
> #if defined(CONFIG_CMD_NET) ...

OK, that's easy. I'll fix that.

> 3) Schmoogie config needs a #undef CONFIG_CMD_EEPROM instead of a
> #define

That's also easy.

> 4) With schmoogie config, schmoogie/dv_board.c fails linking because of 
> missing forceenv(). E.g. in exports.h this is clamped by #ifdef 
> CONFIG_HAS_UID. So I think misc_init_r() in all three dv_board.c need 
> anything similiar.

OK, that is also easy, I'll fix it today.

>
> I will send my updated versions of your patches for reference as answers
> to 
> the individual patch mails. No, I don't want to steal anything. I want
> to 
> help. They resolve 1) - 3), so only (4) is open. Feel free to send them
> again 
> with your Signed-off-by, to ignore them, or use them for update. You 
> mentioned that you are short of time, so hopefully we can avoid to
> invent the 
> wheel two times and reuse stuff already fixed.
>
> For me, then everything else looks okay ;) So I think resolving (4) will
> be 
> the hopefully final version then.
>
> Best regards
>
> Dirk
>

---
******************************************************************
*  KSI at home    KOI8 Net  < >  The impossible we do immediately.  *
*  Las Vegas   NV, USA   < >  Miracles require 24-hour notice.   *
******************************************************************

[U-Boot-Users] [ARM] TI DaVinci support, 2nd attempt [0/5]

[Dirk Behme]

ksi at koi8.net wrote:
> On Tue, 7 Aug 2007, Dirk Behme wrote:
...
>> 1) As with your first set of patches, I can't get patch 2/5 and 4/5 get
>> apply cleanly. I get rejects needing manual resolve for everything 
>> modifying already existing files. All files/patches adding new files 
>> apply
>> cleanly.
> 
> That is extremely strange because the entire patch is made against
> yesterday's git tree. I don't know, may be you guys have some other tree,
> but I made the patch against what I pulled yesterday.

Me too ;)

Seems that the tree version isn't the issue here.

There is some reformatting, either on your side while pasting the 
patches into mail or at my side, while store. Not sure.

It looks to me that each line not starting with a '+' or not empty 
gets an additonal ' ' (space). E.g. in patch 2/5 in file net/eth.c I have

   extern int ns7520_miiphy_initialize(bd_t *bis);
+extern int dm644x_eth_miiphy_initialize(bd_t *bis);

Note the *two* spaces before the first 'extern', while there should be 
only one. Have to check if I can get patch to ignore this.

Best regards

Dirk

[U-Boot-Users] [ARM] TI DaVinci support, 2nd attempt [0/5]

[ksi at koi8.net]

On Tue, 7 Aug 2007, Dirk Behme wrote:

OK, I will post the final version as an attachment in addition to inline
version. This way it should work no matter what.

> ksi at koi8.net wrote:
>> On Tue, 7 Aug 2007, Dirk Behme wrote:
> ...
>>> 1) As with your first set of patches, I can't get patch 2/5 and 4/5
> get
>>> apply cleanly. I get rejects needing manual resolve for everything 
>>> modifying already existing files. All files/patches adding new files
> apply
>>> cleanly.
>> 
>> That is extremely strange because the entire patch is made against
>> yesterday's git tree. I don't know, may be you guys have some other
> tree,
>> but I made the patch against what I pulled yesterday.
>
> Me too ;)
>
> Seems that the tree version isn't the issue here.
>
> There is some reformatting, either on your side while pasting the
> patches 
> into mail or at my side, while store. Not sure.
>
> It looks to me that each line not starting with a '+' or not empty gets
> an 
> additonal ' ' (space). E.g. in patch 2/5 in file net/eth.c I have
>
>  extern int ns7520_miiphy_initialize(bd_t *bis);
> +extern int dm644x_eth_miiphy_initialize(bd_t *bis);
>
> Note the *two* spaces before the first 'extern', while there should be
> only 
> one. Have to check if I can get patch to ignore this.
>
> Best regards
>
> Dirk
>

---
******************************************************************
*  KSI at home    KOI8 Net  < >  The impossible we do immediately.  *
*  Las Vegas   NV, USA   < >  Miracles require 24-hour notice.   *
******************************************************************