Hi Dave,
> When I jump to _start, my code won't even know about u-boot because it is
> located in my code's rwdata section.
>
> Does this sound right?
That's correct. Your kernel will be unaware of u-boot and will just do
what it needs to do. Once the kernel starts, u-boot it out of the picture :-)
> Have you used Redboot? Any opinions?
Only once. It seems fine.
> Any pros or cons of either?
I think it really boils down to support, accessibility, and
features -- you'll really have to look at your requirements and
pick one that best suits your needs.
Personally, I've found u-boot to have a very active and open
user community. User contributions are submitted frequently
and are welcomed ... and the mailing list remains very active.
Ecos/Redboot does not seem as healthy in this regard, HOWEVER,
the FSF is supposed to pick-up ecos ... so I'm sure this won't be
an issue in the future.
Feature-wise, u-boot is clearly ahead of Redboot ... but this doesn't
matter if you don't need the features.
In the end, I think it really boils down to you requirements. I think
both will serve you just fine.
> I'm just wondering if I'm missing something that would pull me one
> way or the other.
I'd be glad to pull you towards u-boot ... but I am admittedly biased ;-)
I don't think you're missing anything ... a bootloader shouldn't make/break the success of your product ... so I think either would be just fine.
Regards,
--Scott