[Openchrome-users] panel size mis-detected on Elonex webbook

[Xavier Bachelot]

Alan Bell wrote:
> should I make a ticket with the patch? I am a bit hesitant because I am
> fairly sure it would break whatever there is out there with this chipset
> and a genuine 1280x800 screen that gets an index of 7 in
> ViaPanelGetNativeModeFromScratchPad 
> Alan.
> 
When Gabriel worked on the panel code, he was had some doubt about the
correctness of this table. Anyway, I think it's probably better to swap
the lines rather than to have twice the same resolution.

File a bug with all the details please, it could be useful to keep the
infos for later.

Regards,
Xavier

> Xavier Bachelot wrote:
>> Alan Bell wrote:
>>  
>>> this is a repost of something I posted a while back, but I am again
>>> interested in an answer to get it working correctly out of the box
>>> with Ubuntu Jaunty.
>>>
>>> I have been working on getting Ubuntu Jaunty to work on the Elonex
>>> webbook laptop, by default the LCD panel does not work at all but the
>>>  external VGA port is operational at 1024x768 (which is the native
>>> resolution of the monitor I attached). I compiled the latest from
>>> trunk and installed that, still didn't work, but with with a lot of
>>> help from schlobinux on IRC I did eventually get it working, it
>>> required a small fix to let the driver know that a panel was there
>>> http://www.openchrome.org/trac/changeset/597/trunk and a modeline in
>>> the xorg.conf to let it know about the 1024x600 resolution of the
>>> panel This left it with a rather odd stretched screen on the panel,
>>> it was running at 1024x600 but this was stretched such that the top
>>> left 820x450 filled the panel. A bit of inspection of Xorg.0.log
>>> revealed that it thought the native panel size was 1280x800 so what
>>> it was really doing was stretching the 1024x600 resolution out to fit
>>> a 1280x800 panel then only displaying 1024x600 of that. The reason it
>>> thought the native size was 1280x800 was because
>>> ViaPanelGetNativeModeFromScratchPad in via_panel.c was getting an
>>> index of 7, which corresponds to 1280x800 in the array at the top of
>>> via_panel.c I hacked line 49 of via_panel.c to read {1024, 600}, and
>>> recompiled. It then worked perfectly. What is a more sensible way to
>>> get this to work? clearly my hack would break something else which
>>> actually does have a 1280x800 panel.
>>>     
>>
>> I see 2 other possibilities :
>> - The value you get from the scratch register is wrong.
>> - The correspondance table is wrong and your change is actually
>> fixing the table.
>>
>>  
>>> Is there somewhere I can put the 1024x600 modeline so that my
>>> xorg.conf can go back to it's almost totally empty state?
>>>
>>> Alan.
>>>
>>>     
>> Can you post a patch against trunk of your modification, please ?
>>
>> Regards,
>> Xavier
>>
>>