All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrik Jakobsson <patrik.r.jakobsson@gmail.com>
To: Kero <kero@chello.nl>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: gma500: Other things that I could work on
Date: Wed, 3 Apr 2013 19:28:31 +0200	[thread overview]
Message-ID: <CAMeQTsZi5hEoQ7PKbAdfynXMZELv39CgOCwfo+baBWvSYjW=bA@mail.gmail.com> (raw)
In-Reply-To: <20130403152116.GB23149@chmeee.dyndns.org>

On Wed, Apr 3, 2013 at 5:21 PM, Kero <kero@chello.nl> wrote:
> Hi,
>
> I would not mind improving use of my Asus EeePC X101CH with Cedar View / gma3600
> a bit more. But a barrier is knowledge of the hardware. Meddling with existing (initialization)
> code is possible, but for point 1 and 3 below that is not going to cut, it, I expect.

It would be very useful if you could help out with cedarview. Even if it's just
by testing patches. A big problem for me is that I don't have the hardware so
it's easy to break things without even knowing about it.

>
> Does anyone have pointers? Who should I talk to about specifications?
> I know Intel is not forthcoming with documentation, yet several people have
> made contributions for poulsbo and later versions of the hardware.
> How did you get the required knowledge?

Most of the mode setting stuff are variations of Intel hardware. You can find
specifications at https://01.org/linuxgraphics/ and it's also useful to look at
the Intel i915 drm driver for reference. It is quite a mix so you need to look
at bits and pieces from several of the Intel generations and try to match them
together.

For the non-Intel parts there are some drivers that never made it into mainline
but is still available online. Some parts are open and some are closed.

There is also a fair amount of guessing and probing needed.

>
> Things I might, in order of personal preference, in due time (after holiday), take a look at:
> 1) would be nice to have the full 1024x600 on the external VGA and HDMI
>    I had a chance to try another monitor over HDMI, same result: only 800x600 visible.
> 2) booting with either VGA or HDMI plugged in, yields two black screens: both the laptop
>    and the monitor. Un- + re-plugging has no visible effect.
> 3) the Fn keys for the backlight induce a response in the backlight, but only with
>    tiny results; /sys/class/backlight/psb-bl/brightness works fine, though
> 4) when using modules, initialization from hibernation is not good enough:
>    my screen stays black; without using modules, the kernel boots normally, and everything is fine.
> 5) initialization from suspend is not good enough: my Asus stays in
>    some text mode (80x25?), but shows garbage (possibly data from the desired console or
>    graphics mode, since sometimes there are reactions correlated to actions)
>    Switching tty or using `chvt` do not improve anything.
>    NB: hibernating and booting solves this.

There are quite a few issues that needs to be addressed and code that needs to
be refactored. I suggest you just dig in and get your hands dirty.

-Patrik

  reply	other threads:[~2013-04-03 17:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-31 11:38 [PATCH] gma500: Make VGA and HDMI connector hotpluggable Kero
2013-04-02 12:54 ` Patrik Jakobsson
2013-04-03 15:21   ` gma500: Other things that I could work on Kero
2013-04-03 17:28     ` Patrik Jakobsson [this message]
2013-04-07 19:24     ` Patrik Jakobsson
2013-04-17 17:57       ` Kero
2013-04-17 22:19         ` Patrik Jakobsson

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='CAMeQTsZi5hEoQ7PKbAdfynXMZELv39CgOCwfo+baBWvSYjW=bA@mail.gmail.com' \
    --to=patrik.r.jakobsson@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kero@chello.nl \
    /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.