From: "Buttchereit, Axel (XL)" <XL@XLsigned.net>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: sylvain.meyer@worldonline.fr, adaplas@pol.net
Subject: Re: [patch] intelfb: add (partial) support for 915G
Date: Wed, 02 Feb 2005 17:40:15 +0100 [thread overview]
Message-ID: <4201026F.1080309@XLsigned.net> (raw)
In-Reply-To: <200502022019.21453.adaplas@hotpop.com>
Antonino A. Daplas wrote:
> On Saturday 29 January 2005 13:11, Buttchereit, Axel (XL) wrote:
>
>>Add (partial) support for 915G
>> No HW cursor at the moment
>> Screen is blanked but signal/sync is not switched off
>>Mostly derived from XFree86/Xorg driver
>>Pass "vesa_modes" and VESA_MODEDB_SIZE in call to "fb_find_mode()"
>> to allow loading as module. Makes "vesa_modes" also the default
>> "modedb" when linking statically into the kernel.
>>Change PREFERRED_MODE to more reasonable value "1024x768-32@70"
>>
>
>
> Can you resend? Patch is malformed.
Sure!
But it would be much easier for me, if I know what's wrong with my patch.
I assume that the kernel source version I was using is wrong (outdated),
i. e. I have to make my patch base on (at least) version 2.6.11-rc2.
I would like to know, if the following statements are true:
@2.6.10 = kernel/v2.6/linux-2.6.10.tar.bz2
@2.6.11-rc1 = @2.6.10 + kernel/v2.6/testing/patch-2.6.11-rc1.bz2
@2.6.11-rc2 = @2.6.10 + kernel/v2.6/testing/patch-2.6.11-rc2.bz2
@2.6.11-rc2-bk1 = @2.6.11-rc2 + kernel/v2.6/snapshots/patch-2.6.11-rc2-bk1.bz2
@2.6.11-rc2-bk2 = @2.6.11-rc2 + kernel/v2.6/snapshots/patch-2.6.11-rc2-bk2.bz2
...
@2.6.11-rc1-mm1 = @2.6.11-rc1 + kernel/people/akpm/patches/2.6/2.6.11-rc1/2.6.11-rc1-mm1/2.6.11-rc1-mm1.bz2
@2.6.11-rc1-mm2 = @2.6.11-rc1 + kernel/people/akpm/patches/2.6/2.6.11-rc1/2.6.11-rc1-mm2/2.6.11-rc1-mm2.bz2
@2.6.11-rc2-mm1 = @2.6.11-rc2 + kernel/people/akpm/patches/2.6/2.6.11-rc2/2.6.11-rc2-mm1/2.6.11-rc2-mm1.bz2
@2.6.11-rc2-mm2 = @2.6.11-rc2 + kernel/people/akpm/patches/2.6/2.6.11-rc2/2.6.11-rc2-mm2/2.6.11-rc2-mm2.bz2
The "2.6.11-rc[V]-bk[W]" are maintained by Linus who integrates patches from Andrews's mm-tree,
i. e. "patch-2.6.11-rc[V]-bk[W]" is a subset (selected patches) from Andrew's current
"2.6.11-rc2-mm[I]" patchset.
Right?
(What about the "-ac" patches? Are they also running into "2.6.11-rc[V]-bk[W]")
Thanks for your patience
--Axel
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
next prev parent reply other threads:[~2005-02-02 16:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-29 5:11 [patch] intelfb: add (partial) support for 915G Buttchereit, Axel (XL)
2005-01-29 12:03 ` Antonino A. Daplas
2005-01-29 15:52 ` Buttchereit, Axel (XL)
2005-02-02 12:30 ` Antonino A. Daplas
2005-02-02 16:40 ` Buttchereit, Axel (XL) [this message]
2005-02-03 4:42 ` Antonino A. Daplas
2005-02-07 4:10 ` Buttchereit, Axel (XL)
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=4201026F.1080309@XLsigned.net \
--to=xl@xlsigned.net \
--cc=adaplas@pol.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=sylvain.meyer@worldonline.fr \
/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;
as well as URLs for NNTP newsgroup(s).