Date: Wed, 09 Apr 2014 11:18:57 +0800 From: Xuebing Wang <xbing6@gmail.com> To: Ian Lepore <ian@FreeBSD.org>, Tim Kientzle <kientzle@FreeBSD.org> Cc: freebsd-arm@FreeBSD.org Subject: Re: [BeagleBone Black Test PATCH 0/2] port latest u-boot Message-ID: <5344BC21.9030109@gmail.com> In-Reply-To: <1396962361.81853.409.camel@revolution.hippie.lan> References: <1396862732-4961-1-git-send-email-xbing6@gmail.com> <C38629E3-59AC-4100-8748-01FF3F4FBC69@freebsd.org> <1396962361.81853.409.camel@revolution.hippie.lan>
next in thread | previous in thread | raw e-mail | index | archive | help
1) I fixed the "kernel reboots every 50 seconds issue" by disable Watchdog.
AM335x Watchdog is enabled by below commit in mainline u-boot. It is
written on Oct 1 2013.
commit 6843918e0035bf06cb65ad2b4c98b38e86e43bd5
Author: Tom Rini <trini@ti.com>
Date: Tue Oct 1 12:32:04 2013 -0400
am335x: Enable CONFIG_OMAP_WATCHDOG support
There is a board-specific portion for calling watchdog enable
itself, in
main U-Boot.
Signed-off-by: Tom Rini <trini@ti.com>
2) Do we consider to port the latest u-boot?
On 04/08/2014 09:06 PM, Ian Lepore wrote:
> On Mon, 2014-04-07 at 18:41 -0700, Tim Kientzle wrote:
>> On Apr 7, 2014, at 2:25 AM, Xuebing Wang <xbing6@gmail.com> wrote:
>>
>>> Hi Tim and all,
>>>
>>> This is for discussion only. Would you please advice?
>>>
>>> This is motivated by trying to increase CPU frequency for BeagleBone Black.
>>>
>>> AM335x cpufreq is not supported yet. In order to achieve the goal to increase
>>> CPU freq, I am thinking of a 2-step approach:
>>> 1) port latest u-boot, which have cpufreq better organized
>>> 2) tweak u-boot opp/freq later
>> Setting the processor frequency after the OS is running
>> is not difficult. The AM335x TRM shows exactly how to do it.
>>
>> I would not change U-Boot but rather implement
>> a FreeBSD driver that exposed a read/write sysctl
>> to reprogram the CPU frequency.
>>
>> Getting powerd to work with this should be straightforward.
>>
>> Tim
>>
> I agree with this, we should handle the frequency change in the kernel
> rather than in u-boot.
>
> On the other hand, I'm all for updating to a newer u-boot for other
> reasons. I did that for imx6, updating to 2014.01 in place of the
> 2013.04 that wandboard was using, and it went well. In fact, pretty
> much all I had to do was remove all the patches I had been using for
> 2013.04 except for turning on the API option and a couple other options.
> There apparently have been recent fixes to some of the API stuff, such
> as how storage devices are enumerated, which will help with the new
> features added to ubldr that let you choose which device to load the
> kernel from with u-boot env vars.
>
> -- Ian
>
>
>
--
Thanks,
Xuebing Wang
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5344BC21.9030109>