From: linux@johnea.net
To: linux-omap@vger.kernel.org
Subject: Re: Which git to clone for testing prior to submitting bugs?
Date: Thu, 27 Sep 2012 13:16:29 -0700 [thread overview]
Message-ID: <5064B41D.9030709@johnea.net> (raw)
In-Reply-To: <CAOCHtYiido11MG55m601CX2isYJ2oFcubgJ7Wkng=HnkT_DdcQ@mail.gmail.com>
On 09/27/2012 12:39 PM, Robert Nelson wrote:
>>
>> So, i would first look at the config (zcat /proc/config.gz) between
>> those two releases, and if the arch developers added any more patches
>> to it..
>
> https://github.com/archlinuxarm/PKGBUILDs/commit/68a9e5a1609fde10a2f31dac8df211f0c3874eb7
>
> It looks like they disabled CONFIG_OMAP_RESET_CLOCKS
>
> I'm pretty sure that would force you to be stuck with what ever u-boot
> sets up for those pins...
Thank you very much Robert!
I found this in your 3.5 series patchset logs:
"beagle: video works now, had to drop the hi-speed pll divider, as the infastructure for it looks to have been removed"
https://github.com/RobertCNelson/stable-kernel/commit/e7c8d9e8894997ae6a1ad9c83292ed75c5ac32c5
Which makes me think 3.5.4 on the beagle with your patches will have DVI again.
I just received a kernel to test from the archlinuxarm devs, if spidev is still missing, I'll pass along your advice regarding CONFIG_OMAP_RESET_CLOCKS.
Thanks again for your help! I'll follow up with the results...
johnea
next prev parent reply other threads:[~2012-09-27 20:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 17:19 Which git to clone for testing prior to submitting bugs? linux
2012-09-27 18:25 ` Robert Nelson
2012-09-27 18:56 ` linux
2012-09-27 18:55 ` Felipe Balbi
2012-09-27 19:17 ` Tony Lindgren
2012-09-27 19:27 ` Robert Nelson
2012-09-27 19:39 ` Robert Nelson
2012-09-27 20:16 ` linux [this message]
2012-09-27 20:41 ` Robert Nelson
2012-09-28 18:49 ` linux
2012-09-28 19:18 ` Robert Nelson
2012-09-28 19:46 ` linux
2012-10-01 14:57 ` johnea
2012-10-01 16:50 ` Robert Nelson
2012-10-01 16:57 ` linux
2012-10-01 21:16 ` linux
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=5064B41D.9030709@johnea.net \
--to=linux@johnea.net \
--cc=linux-omap@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox