[Xorg-driver-geode] Geode LX video testing results

[Brunner, Brian T.]

Hello

I did not subscribe to this list, but got "auto-subscribed".
I am not pleased at the presumption.
I attempted to unsubscribe, but no success.

Somebody else gets to unsubscribe me, as I will auto-respond to this
list.

(auto-subscribe isn't rude?  Neither is auto-respond)
 

> -----Original Message-----
> From: xorg-driver-geode-bounces at lists.x.org 
> [mailto:xorg-driver-geode-bounces at lists.x.org] On Behalf Of 
> Bart Trojanowski
> Sent: Thursday, December 13, 2007 10:08 PM
> To: xorg-driver-geode at lists.x.org
> Subject: Re: [Xorg-driver-geode] Geode LX video testing results
> 
> * Bart Trojanowski <bart at jukie.net> [071213 17:26]:
> > > What that function tries to do is map the VGA space and 
> look for a 
> > > VGA signature (which won't be there on LinuxBIOS 
> implementations), 
> > > and then behaves accordingly.  Apparently its not working on some 
> > > BIOSes, but is working on others, which leads me to believe that 
> > > this might be a memory problem somewhere along the line.
> > 
> > The log is pretty useless when it comes to the freeze case. 
>  I'll try 
> > to get you better information as to where the code actually freezes.
> 
> I was getting problem running gdbserver with X.  SIGTRAP errors.
> I said I wasn't an X developer... indeed I am from the kernel 
> world, so as a result I am really really good at printk() debugging :)
> 
> So using what I know, I wrote some code to send a TCP log 
> messages with TCP_NODELAY and for good measure an fsync() 
> after each message.  Then I sprinkled log messages printing 
> the __LINE__ number all over LXPreInit().  Barbaric, I know.
> 
> Anyway, I am using the patched version.  And I didn't put in 
> my useVGA=FALSE hack as I wanted it to freeze.
> 
> Running X -configure I get a freeze inside the call to
> 
>         GeodeProbeDDC(pScrni, pEnt->index);
> 
> Running X -config xorg.conf I get a freeze inside the same call.
> 
> Then I added a short sleep call in my TCP log function, 
> essentially adding a delay between each function call made by 
> LXPreInit(). And, I was very surprised to find out that X 
> came up, and in 1024x768 no less.
> 
> I didn't trust my results, so I ran it again a few more 
> times.  Same result.  Xorg.0.log attached.
> 
> Anyway, it may just be that one of the things we probe needs 
> a timeout that we are not giving it.  From all the hardware 
> I've worked with, this is a quite common requirement after a 
> reset or reconfiguration operation.  I will try to narrow it 
> down tomorrow.
> 
> -Bart
> 
> -- 
> 				WebSig: http://www.jukie.net/~bart/sig/
> 

*******************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept
for the presence of computer viruses.

www.Hubbell.com - Hubbell Incorporated