From: linux@johnea.net
To: Robert Nelson <robertcnelson@gmail.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: Which git to clone for testing prior to submitting bugs?
Date: Fri, 28 Sep 2012 11:49:34 -0700 [thread overview]
Message-ID: <5065F13E.8070306@johnea.net> (raw)
In-Reply-To: <CAOCHtYjjczpQ0oJ4zgrExdF7C-OAsfzMLwAEfdExkFG2uiUKgw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2453 bytes --]
On 09/27/2012 01:41 PM, Robert Nelson wrote:
> On Thu, Sep 27, 2012 at 3:16 PM,<linux@johnea.net> wrote:
>> 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..
>>>
>>>
>>> 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...
Corrected, now: CONFIG_OMAP_RESET_CLOCKS=y
>>
>> "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
>>
>
> Correct, dropping that specific patch (1), got 3.5.x working on my
> beagle again. .( i was distracted with an another project, so i was a
> little late in testing/stabilizing 3.5.x when porting the v3.4.x
> patchset ;) ..)
>
3.5.4 is booting on beagle xM with the patchset:
http://rcn-ee.net/deb/sid-armhf/v3.5.4-x6/patch-3.5.4-x6.diff.gz
buddy=spidev is working again (Thank You)
However I'm still not seeing DVI console 8-(
These messages appear during boot:
[ 0.000000] Kernel command line: console= mpurate=auto buddy=spidev camera=none vram=18MB omapfb.mode=dvi:800x480MR-24@60 omapfb.vram=0:6M,1:6M,2:6M omapdss.def_disp=dvi root=/dev/mmcblk0p2 rootfstype=ext2 rootwait
[ 0.190155] Could not look up dss_hdmi hw_mod
[ 10.605987] omapdrm: module is from the staging directory, the quality is unknown, you have been warned.
[ 10.682647] omapdrm omapdrm.0: DMM not available, disable DMM support
[ 10.682739] omapdrm omapdrm.0: dvi has no driver.. skipping it
[ 10.682769] omapdrm omapdrm.0: lcd has no driver.. skipping it
[ 10.815246] fb0: omapdrm frame buffer device
[ 10.815338] [drm] Initialized omapdrm 1.0.0 20110917 on minor 0
Once booted, /dev/fb0 is present, but no fb1 or fb2.
The display never even blinks during reboot. No console output appears when I use "console=" and a login prompt is never presented.
Attached are config.gz from running system and gz'd complete dmesg output (hope attachments are OK on the list).
There's another 3.5.4 build scheduled on the panda build farm this afternoon. If you have any config modification suggestions, they'd be very gratefully received.
Thanks again for your insight!
johnea
[-- Attachment #2: config-3.5.4-archarm.gz --]
[-- Type: application/gzip, Size: 23130 bytes --]
[-- Attachment #3: dmesg-3.5.4.txt.gz --]
[-- Type: application/gzip, Size: 7329 bytes --]
next prev parent reply other threads:[~2012-09-28 18:49 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
2012-09-27 20:41 ` Robert Nelson
2012-09-28 18:49 ` linux [this message]
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=5065F13E.8070306@johnea.net \
--to=linux@johnea.net \
--cc=linux-omap@vger.kernel.org \
--cc=robertcnelson@gmail.com \
/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