* [U-Boot] v2015.04-rc4: broken for custom TI-based board
@ 2015-03-18 18:07 Peter Kuemmel
2015-03-19 7:11 ` Igor Grinberg
0 siblings, 1 reply; 5+ messages in thread
From: Peter Kuemmel @ 2015-03-18 18:07 UTC (permalink / raw)
To: u-boot
I have a custom board which boots with a patched
cm_t35 configuration based on the v2015.01 release.
When I update to v2015.04-rc4 the system reboots
after the x-loader has read u-boot from MMC and
started it.
Does someone has an idea which change could be
responsible for this?
Many thanks,
Peter
^ permalink raw reply [flat|nested] 5+ messages in thread
* [U-Boot] v2015.04-rc4: broken for custom TI-based board
2015-03-18 18:07 [U-Boot] v2015.04-rc4: broken for custom TI-based board Peter Kuemmel
@ 2015-03-19 7:11 ` Igor Grinberg
2015-03-19 10:43 ` Peter Kuemmel
0 siblings, 1 reply; 5+ messages in thread
From: Igor Grinberg @ 2015-03-19 7:11 UTC (permalink / raw)
To: u-boot
Hi Peter,
On 03/18/15 20:07, Peter Kuemmel wrote:
> I have a custom board which boots with a patched
> cm_t35 configuration based on the v2015.01 release.
>
> When I update to v2015.04-rc4 the system reboots
> after the x-loader has read u-boot from MMC and
> started it.
IIUC, we have a working v2015.01 and non working v2015.04-rc4?
>
> Does someone has an idea which change could be
> responsible for this?
Not sure. May be you can run a quick git bisect?
v2015.01 .. v2015.04-rc4 shouldn't be too much.
--
Regards,
Igor.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [U-Boot] v2015.04-rc4: broken for custom TI-based board
2015-03-19 7:11 ` Igor Grinberg
@ 2015-03-19 10:43 ` Peter Kuemmel
2015-03-19 12:11 ` Igor Grinberg
0 siblings, 1 reply; 5+ messages in thread
From: Peter Kuemmel @ 2015-03-19 10:43 UTC (permalink / raw)
To: u-boot
> Gesendet: Donnerstag, 19. M?rz 2015 um 08:11 Uhr
> Von: "Igor Grinberg" <grinberg@compulab.co.il>
> An: "Peter Kuemmel" <syntheticpp@gmx.net>, u-boot at lists.denx.de
> Cc: "Nikita Kiryanov" <nikita@compulab.co.il>
> Betreff: Re: [U-Boot] v2015.04-rc4: broken for custom TI-based board
>
> Hi Peter,
>
> On 03/18/15 20:07, Peter Kuemmel wrote:
> > I have a custom board which boots with a patched
> > cm_t35 configuration based on the v2015.01 release.
> >
> > When I update to v2015.04-rc4 the system reboots
> > after the x-loader has read u-boot from MMC and
> > started it.
>
> IIUC, we have a working v2015.01 and non working v2015.04-rc4?
>
> >
> > Does someone has an idea which change could be
> > responsible for this?
>
> Not sure. May be you can run a quick git bisect?
> v2015.01 .. v2015.04-rc4 shouldn't be too much.
After bisecting it figures out that the default configuration
does not work: I have to disable "Enable Driver Model for serial drivers"
But still have to enable the "Driver Model", even without any other drivers
are selected. (Seems I have to read some documentation about the driver model).
Thanks,
Peter
>
>
> --
> Regards,
> Igor.
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* [U-Boot] v2015.04-rc4: broken for custom TI-based board
2015-03-19 10:43 ` Peter Kuemmel
@ 2015-03-19 12:11 ` Igor Grinberg
2015-03-28 15:11 ` Simon Glass
0 siblings, 1 reply; 5+ messages in thread
From: Igor Grinberg @ 2015-03-19 12:11 UTC (permalink / raw)
To: u-boot
On 03/19/15 12:43, Peter Kuemmel wrote:
>> Gesendet: Donnerstag, 19. M?rz 2015 um 08:11 Uhr
>> Von: "Igor Grinberg" <grinberg@compulab.co.il>
>> An: "Peter Kuemmel" <syntheticpp@gmx.net>, u-boot at lists.denx.de
>> Cc: "Nikita Kiryanov" <nikita@compulab.co.il>
>> Betreff: Re: [U-Boot] v2015.04-rc4: broken for custom TI-based board
>>
>> Hi Peter,
>>
>> On 03/18/15 20:07, Peter Kuemmel wrote:
>>> I have a custom board which boots with a patched
>>> cm_t35 configuration based on the v2015.01 release.
>>>
>>> When I update to v2015.04-rc4 the system reboots
>>> after the x-loader has read u-boot from MMC and
>>> started it.
>>
>> IIUC, we have a working v2015.01 and non working v2015.04-rc4?
>>
>>>
>>> Does someone has an idea which change could be
>>> responsible for this?
>>
>> Not sure. May be you can run a quick git bisect?
>> v2015.01 .. v2015.04-rc4 shouldn't be too much.
>
> After bisecting it figures out that the default configuration
> does not work: I have to disable "Enable Driver Model for serial drivers"
> But still have to enable the "Driver Model", even without any other drivers
> are selected. (Seems I have to read some documentation about the driver model).
Adding Simon to Cc.
Simon, can you please shed some light on this?
--
Regards,
Igor.
^ permalink raw reply [flat|nested] 5+ messages in thread
* [U-Boot] v2015.04-rc4: broken for custom TI-based board
2015-03-19 12:11 ` Igor Grinberg
@ 2015-03-28 15:11 ` Simon Glass
0 siblings, 0 replies; 5+ messages in thread
From: Simon Glass @ 2015-03-28 15:11 UTC (permalink / raw)
To: u-boot
Hi,
On 19 March 2015 at 06:11, Igor Grinberg <grinberg@compulab.co.il> wrote:
> On 03/19/15 12:43, Peter Kuemmel wrote:
>>> Gesendet: Donnerstag, 19. M?rz 2015 um 08:11 Uhr
>>> Von: "Igor Grinberg" <grinberg@compulab.co.il>
>>> An: "Peter Kuemmel" <syntheticpp@gmx.net>, u-boot at lists.denx.de
>>> Cc: "Nikita Kiryanov" <nikita@compulab.co.il>
>>> Betreff: Re: [U-Boot] v2015.04-rc4: broken for custom TI-based board
>>>
>>> Hi Peter,
>>>
>>> On 03/18/15 20:07, Peter Kuemmel wrote:
>>>> I have a custom board which boots with a patched
>>>> cm_t35 configuration based on the v2015.01 release.
>>>>
>>>> When I update to v2015.04-rc4 the system reboots
>>>> after the x-loader has read u-boot from MMC and
>>>> started it.
>>>
>>> IIUC, we have a working v2015.01 and non working v2015.04-rc4?
>>>
>>>>
>>>> Does someone has an idea which change could be
>>>> responsible for this?
>>>
>>> Not sure. May be you can run a quick git bisect?
>>> v2015.01 .. v2015.04-rc4 shouldn't be too much.
>>
>> After bisecting it figures out that the default configuration
>> does not work: I have to disable "Enable Driver Model for serial drivers"
>> But still have to enable the "Driver Model", even without any other drivers
>> are selected. (Seems I have to read some documentation about the driver model).
>
> Adding Simon to Cc.
> Simon, can you please shed some light on this?
If you look in this file there is platform data for the serial port:
arch/arm/cpu/armv7/am33xx/board.c
U_BOOT_DEVICES(am33xx_uarts) = {
...
Do you think this might be missing for this board?
For the omap3 boards it is supported to be here:
arch/arm/cpu/armv7/omap3/board.c
But perhaps for some reason it is not included?
Regards,
Simon
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2015-03-28 15:11 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-03-18 18:07 [U-Boot] v2015.04-rc4: broken for custom TI-based board Peter Kuemmel
2015-03-19 7:11 ` Igor Grinberg
2015-03-19 10:43 ` Peter Kuemmel
2015-03-19 12:11 ` Igor Grinberg
2015-03-28 15:11 ` Simon Glass
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox