All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Miata <mrmazda@earthlink.net>
To: intel-gfx@lists.freedesktop.org
Subject: Re: Using quirks to fix incorrect Monitor physical size
Date: Mon, 13 Sep 2010 09:16:02 -0400	[thread overview]
Message-ID: <4C8E2412.7080908@earthlink.net> (raw)
In-Reply-To: <848094323.727859.1284378142343.JavaMail.root@sz0115a.westchester.pa.mail.comcast.net>

On 2010/09/13 11:42 (GMT) Nasa composed:

> This isn't a laptop.  It's a 7" monitor (http://www.lilliput.cn/EBY701-NP.html),
> that I am using in my carpc.  I am presently try this with the IVI 
> version of meego (with it's own issues).  Lilliput does provided drivers
> for Windows, but nothing directly for Linux.  I have also verified that the 
> monitor doesn't provide EDID data as the file size (I found were it's dump to, 
> just can't recall right now) was 0.  Talking to Lilliput themselves hasn't 
> been very helpful (I don't speak a 2nd language, and neither did the rep I
> tried to talk too).

Anything that is neither a standard format (4:3, 16:10 or 16:9) nor provides
valid EDID is just plain broken. I'd return it. If it's too late for free
return, maybe the vendor would allow exchange. If not, then try warranty
repair. Maybe a Lilliput support manager can authorize an attempt to get it
to output valid EDID either with a firmware update or otherwise.

Again, what about VESA or FBDEV drivers? No help?
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409

Felix Miata  ***  http://fm.no-ip.com/

  reply	other threads:[~2010-09-13 13:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <631910804.725536.1284372575092.JavaMail.root@sz0115a.westchester.pa.mail.comcast.net>
2010-09-13 10:10 ` Using quirks to fix incorrect Monitor physical size Nasa
2010-09-13 11:14   ` Felix Miata
2010-09-13 11:42     ` Nasa
2010-09-13 13:16       ` Felix Miata [this message]
2010-09-13 13:44       ` The Fungi
     [not found] <1524502115.868672.1284559892980.JavaMail.root@sz0115a.westchester.pa.mail.comcast.net>
2010-09-15 14:18 ` Nasa
     [not found] <728542343.735537.1284385743146.JavaMail.root@sz0115a.westchester.pa.mail.comcast.net>
2010-09-13 13:57 ` Nasa
2010-09-13 21:58   ` Felix Miata
2010-09-13 22:42     ` Nasa
2010-09-15 13:53       ` Felix Miata
     [not found] <439980487.671370.1284230896263.JavaMail.root@sz0115a.westchester.pa.mail.comcast.net>
2010-09-11 18:56 ` Nasa

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=4C8E2412.7080908@earthlink.net \
    --to=mrmazda@earthlink.net \
    --cc=intel-gfx@lists.freedesktop.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.