From: Alexander Kern <alex.kern@gmx.de>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Re: still ..Confused about atyfb and M1
Date: Sun, 8 Feb 2004 21:42:02 +0100 [thread overview]
Message-ID: <200402082142.02820.alex.kern@gmx.de> (raw)
In-Reply-To: <Pine.GSO.4.58.0402071852500.19574@waterleaf.sonytel.be>
Am Samstag, 7. Februar 2004 18:54 schrieb Geert Uytterhoeven:
> On Fri, 6 Feb 2004, Richard Smith wrote:
> > Geert Uytterhoeven wrote:
> > > 01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobility
> > > P/M AGP 2x (rev 64) (prog-if 00 [VGA]) Subsystem: Sony Corporation:
> > > Unknown device 80c7
> > > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> > > ParErr- Stepping+ SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+
> > > ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- Latency:
> > > 66 (2000ns min), Cache Line Size: 0x08 (32 bytes) Interrupt: pin A
> > > routed to IRQ 9
> > > Region 0: Memory at fd000000 (32-bit, non-prefetchable)
> > > [size=16M]
> >
> > I don't think your chip is an M1. The M1 is limited to 8 Megs of memory
> > which is on chip and not expandable so I don't see how you can have
> > 16Megs.
>
> It has 8 MiB of RAM.
>
> All Mach64 PCI/AGP variants show 16 MiB of PCI memory space, for up to 8
> MiB of video RAM. The second 8 MiB is the big endian aperture.
>
> Gr{oetje,eeting}s,
>
> Geert
Hallo all,
I'm not understand, what a problem is, who is problem reporter and why
he don't ask me?
I work on this driver for 2.6 kernel and it works good on my ARMADA E500
It's 15" 1400x1050 natural with
ATI Technologies Inc Rage Mobility P/M AGP 2x (rev 64)
good means all resolutions, from 320x200 to 1600x1200(that one only on CRT).
Regards Alex
P.S.
If everybody has a problem, please be sure, you use the last code from James's
fbdev.diff.gz, than switch debug define in atyfb_base.c on and
send me a log.
-------------------------------------------------------
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-02-08 20:42 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
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 [this message]
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=200402082142.02820.alex.kern@gmx.de \
--to=alex.kern@gmx.de \
--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 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).