geode: Add a VSA2 ID for General Software

Kushal Koolwal kushalkoolwal at hotmail.com
Fri Jun 13 15:19:34 EDT 2008


> Well, now you can send us all the information I asked for before.
See below for all the info.

> Step 1 is to try a kernel from GIT HEAD.
Taken. 2.6.26-rc6

> Step 2 is to send us the complete dmesg output.  What BIOS are you using?
See the attached file. General Software BIOS.
 
> Step 3 is to send us the fbset information from a broken system
debian:~# fbset -i
mode "1024x768-60"
    # D: 64.998 MHz, H: 48.362 kHz, V: 60.002 Hz
    geometry 1024 768 1024 768 16
    timings 15385 160 24 29 3 136 6
    hsync high
    vsync high
    rgba 5/11,6/5,5/0,0/0
endmode
Frame buffer device information:
    Name        : Geode LX
    Address     : 0xe0000000
    Size        : 33554432
    Type        : PACKED PIXELS
    Visual      : TRUECOLOR
    XPanStep    : 0
    YPanStep    : 0
    YWrapStep   : 0
    LineLength  : 2048
    Accelerator : No
debian:~# 
 
> step 4 is to tell us what your monitor thinks it is driving (there is usually
>a information button that says what the current xres yres and refresh is).
HFreq:48.5
VFreq: 60.3
Pixel Clock:65.2
Resolution:1024x768
Monitor:ViewSonic VE510b

 
> Step 5 is to compile up the the MSR tools from hpa
> http://www.kernel.org/pub/linux/utils/cpu/msr-tools/
> And connect via serial or net to the system when it is broken and 
> send the value of MSR 0x4C000015.
debian:~# rdmsr 0x4C000015
421402000000
debian:~#

> Step 6 is to send the complete output of
> /sys/devices/pci0000:00/0000:00:01.1/resource
debian:~# cat /sys/devices/pci0000:00/0000:00:01.1/resource
0x00000000e0000000 0x00000000e1ffffff 0x0000000000020200
0x00000000e2000000 0x00000000e2003fff 0x0000000000020200
0x00000000e2004000 0x00000000e2007fff 0x0000000000020200
0x00000000e2008000 0x00000000e200bfff 0x0000000000020200
0x00000000e200c000 0x00000000e200ffff 0x0000000000020200
0x0000000000000000 0x0000000000000000 0x0000000000000000
0x0000000000000000 0x0000000000000000 0x0000000000000002
debain:~# 

Please let me know if you need any further information.
Kushal Koolwal

I do blog at http://blogs.koolwal.net/



______________________
 EMAILING FOR THE GREATER GOOD

> Date: Fri, 13 Jun 2008 13:07:11 -0600
> From: jordan.crouse at amd.com
> To: kushalkoolwal at hotmail.com
> CC: linux-geode at bombadil.infradead.org; dilinger at queued.net
> Subject: Re: geode:  Add a VSA2 ID for General Software
> 
> On 13/06/08 11:19 -0700, Kushal Koolwal wrote:
> > Jordan,
> > 
> > I tried the patch and this time lxfb does detect the device but then I am still seeing the green lines during the boot.
> > 
> > I am attaching my full dmesg output. Here is a relevant part of the output:
> > [    0.173435] GEODE: VSA SIG = 534d
> > [    0.173507] GEODE:  Read from VSA
> > [    0.178915] lxfb 0000:00:01.1: 32768 KB of video memory at 0xe0000000
> > [    0.199949] fb0: Geode LX frame buffer device
> > 
> > I still think there might be something else going on in addition to this because I can get the lxfb working just fine on a 2.6.24 Debian Kernel.
> > 
> > Thank you once again for your time. Please let me know if I can be of any assistance in further debugging this issue.
>  
> Well, now you can send us all the information I asked for before.
> 
> Jordan
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://bombadil.infradead.org/pipermail/linux-geode/attachments/20080613/f660e6ad/attachment-0001.html 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: dmesg_lxfb_vsa_patch.txt
Url: http://bombadil.infradead.org/pipermail/linux-geode/attachments/20080613/f660e6ad/attachment-0001.txt 


More information about the Linux-geode mailing list