From: lbg_147@bluebottle.com
To: intel-gfx@lists.freedesktop.org
Subject: NM10 chipset with GMA3600
Date: Thu, 03 May 2012 12:16:26 +0000 [thread overview]
Message-ID: <1336047386.4fa2771aebab1@mail.bluebottle.com> (raw)
Hello everyone,
I'm writing to this list, hoping not to be in the wrong place. The subject is a GMA 3600 graphic controller which I have on a D2500CC Mini-ITX Intel board. My operating system is Debian Wheezy with latest stable 3.3.4 kernel (GMA3600 option compiled in).
According to Intel's positive reputation for supporting open source drivers, I admit I didn't do a thorough research on this specific chipset *before* buying the mainboard (and that's my fault). Only later, being stuck to a Vesa driver with wrong screen ratio and resolution, I discovered that GMA3600 isn't supported (yet).
My question is: will it ever be, as GMA3150 is? Or I'd better switch to an H67 chipset with HD controller?
Many, many thanks.
Best regards,
Andrew
next reply other threads:[~2012-05-03 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 12:16 lbg_147 [this message]
2012-05-07 5:37 ` NM10 chipset with GMA3600 Zhenyu Wang
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=1336047386.4fa2771aebab1@mail.bluebottle.com \
--to=lbg_147@bluebottle.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox