From: Igor Grinberg <grinberg@compulab.co.il>
To: u-boot@lists.denx.de
Subject: [U-Boot] v2015.04-rc4: broken for custom TI-based board
Date: Thu, 19 Mar 2015 14:11:47 +0200 [thread overview]
Message-ID: <550ABD03.3010604@compulab.co.il> (raw)
In-Reply-To: <trinity-0b9c752c-f90b-4a13-bff7-cbeec209fac1-1426761789471@3capp-gmx-bs11>
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.
next prev parent reply other threads:[~2015-03-19 12:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2015-03-28 15:11 ` 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=550ABD03.3010604@compulab.co.il \
--to=grinberg@compulab.co.il \
--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