From: Richard Smith <rsmith@bitworks.com>
To: benh@kernel.crashing.org
Cc: Alexander Kern <alex.kern@gmx.de>, Jon Smirl <jonsmirl@yahoo.com>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>,
James Simmons <jsimmons@infradead.org>
Subject: Re: still ..Confused about atyfb and M1
Date: Tue, 27 Jan 2004 18:07:18 -0600 [thread overview]
Message-ID: <4016FD36.6010109@bitworks.com> (raw)
In-Reply-To: <400C8907.6080809@bitworks.com>
Richard Smith wrote:
> Benjamin Herrenschmidt wrote:
>
>>> Mach64 MOBILITY M1 works by me for ages. I submitted all patches to
>>> James for months. They are in fbdev.diff.gz. But I dont think, they
>>> will be merged with vanilla very soon.
>>
>>
> I grabbed fbdev.diff.gz from infradead (is this the canonical source?)
> and patched my 2.6.1 tree. But I still don't see my 0x4c52 device id
> listed in the tables.
>
And it still dosen't detect my device(s).
I never received an answer to this. I don't see how the M1 can work
supported when the device id isn't in the table. Did I really get the
latest patch?
--
Richard A. Smith
rsmith@bitworks.com
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next prev parent reply other threads:[~2004-01-28 0:08 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-17 0:23 Fwd: [PATCH] ATI Mach64 accelerated imgblit (sligthly improved) Alexander Kern
2004-01-17 4:26 ` Confused about atyfb status Richard Smith
2004-01-17 6:38 ` Jon Smirl
2004-01-17 7:31 ` Richard Smith
2004-01-17 12:03 ` Alexander Kern
2004-01-18 22:52 ` Benjamin Herrenschmidt
2004-01-20 1:48 ` still ..Confused about atyfb and M1 Richard Smith
2004-01-28 0:07 ` Richard Smith [this message]
2004-01-30 21:47 ` James Simmons
2004-02-03 19:16 ` Richard Smith
2004-02-04 9:06 ` Geert Uytterhoeven
2004-02-04 15:16 ` Richard Smith
2004-02-04 15:35 ` Geert Uytterhoeven
2004-02-05 17:55 ` Richard Smith
2004-02-05 20:16 ` Geert Uytterhoeven
2004-02-05 21:37 ` Richard Smith
2004-02-05 22:57 ` Benjamin Herrenschmidt
2004-02-06 0:22 ` Richard Smith
2004-02-06 9:17 ` Geert Uytterhoeven
2004-02-06 20:13 ` Richard Smith
2004-02-07 17:54 ` Geert Uytterhoeven
2004-02-08 20:42 ` Alexander Kern
2004-02-09 22:51 ` Richard Smith
2004-02-06 23:30 ` James Simmons
2004-02-06 23:42 ` Richard Smith
2004-02-04 15:18 ` Richard Smith
2004-02-04 15:36 ` Geert Uytterhoeven
2004-02-04 23:29 ` Benjamin Herrenschmidt
2004-02-03 22:18 ` Richard Smith
2004-01-17 18:36 ` Confused about atyfb status Geert Uytterhoeven
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=4016FD36.6010109@bitworks.com \
--to=rsmith@bitworks.com \
--cc=alex.kern@gmx.de \
--cc=benh@kernel.crashing.org \
--cc=jonsmirl@yahoo.com \
--cc=jsimmons@infradead.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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.