From: Darren Hart <dvhart@linux.intel.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: yocto@yoctoproject.org
Subject: Re: [PATCH 0/1] Enable to set RTC for beagleboard
Date: Wed, 15 Jun 2011 10:33:04 -0700 [thread overview]
Message-ID: <4DF8ECD0.8090900@linux.intel.com> (raw)
In-Reply-To: <4DF8E369.10000@windriver.com>
On 06/15/2011 09:52 AM, Bruce Ashfield wrote:
> On 06/15/11 12:48, Darren Hart wrote:
>>
>>
>> On 06/15/2011 06:31 AM, Bruce Ashfield wrote:
>>> On 06/15/11 09:25, Koen Kooi wrote:
>>>>
>>>> Op 15 jun 2011, om 15:21 heeft Bruce Ashfield het volgende
>>>> geschreven:
>>>>
>>>>> On 06/15/11 06:41, Jingdong Lu wrote:
>>>>>> From: Jingdong Lu<jingdong.lu@windriver.com>
>>>>>>
>>>>>> Ensure msecure is mux'd to be able to set the RTC for
>>>>>> beagleboard. Fixes bug [YOCTO #767]
>>>>>
>>>>> Jingdong,
>>>>>
>>>>> The fix looks reasonable to me, Darren has been refreshing the
>>>>> beagleboard support as well, so I've cc'd him here to see if we
>>>>> have this change present in the work in progress trees.
>>>>>
>>
>>
>> I do not have something similar queued.
>>
>>
>>>>> What tests did you run to ensure that the RTC worked on the
>>>>> beagleboard ? There was some debate around whether or not you
>>>>> needed an add-on card to get this functionality available ?
>>>>
>>>> You need to remove some resistors and add a battery, or add an
>>>> expansionboard like the zippy or zippy2, which have a DS1307 RTC
>>>> with battery.
>>>
>>> Thanks Koen,
>>>
>>> This confirms what I thought (zippy*), so clearly this is either a
>>> board with that setup, or runtime testing was .. unique. Either way,
>>> more details and research is needed for this one.
>>
>>
>> I'll wait to hear upstream status on this. Given the requirements for
>> use, I wouldn't mind just closing 767 as will not fix as it can't work
>> with the beagleboard out of the box anyway.
>
> I'm ok with that resolution .. for the bug. But if the patch
> isn't already in another upstream tree, it's worth having
> (if benign to the rest of the variants) and then we can get
> it sent upstream from there.
>
> I can change the bug's status if you like.
I want to hear back from Jingdong regarding this patch first. Is this
new code? If so, then yes, let's get it to mainline as Bruce suggested.
>
> Cheers,
>
> Bruce
>
>>
>>
>> --
>> Darren
>>
>>> Cheers,
>>>
>>> Bruce
>>>
>>>>
>>>> regards,
>>>>
>>>> Koen
>>>
>>> _______________________________________________ yocto mailing list
>>> yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
>>
>
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-06-15 17:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-15 10:41 [PATCH 0/1] Enable to set RTC for beagleboard Jingdong Lu
2011-06-15 10:41 ` [PATCH 1/1] RTC: Enable to set RTC Jingdong Lu
2011-06-15 13:21 ` [PATCH 0/1] Enable to set RTC for beagleboard Bruce Ashfield
2011-06-15 13:25 ` Koen Kooi
2011-06-15 13:31 ` Bruce Ashfield
2011-06-15 16:48 ` Darren Hart
2011-06-15 16:52 ` Bruce Ashfield
2011-06-15 17:33 ` Darren Hart [this message]
2011-06-16 2:23 ` Lu Jingdong
2011-06-16 4:25 ` Bruce Ashfield
2011-06-16 14:45 ` Darren Hart
2011-06-16 14:59 ` Koen Kooi
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=4DF8ECD0.8090900@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=bruce.ashfield@windriver.com \
--cc=yocto@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.