I thought most of the GATOS stuff had been merged into 4.3. At least I
have had no problems with Xv on my Radeon 7000 with XFree86 4.3.0 and
I seem to recall that support was claimed for all Radeons except,
perhaps the 9500.
Perhaps for other cards, but there's still no native Xv support for
You might want to try the Gatos drivers from http://gatos.sourceforge.net/ .
With this driver, I got the ATi chipset in my laptop working with Xv support.
I've just visited the page. Looks promising, indeed, but I'm a bit puzzled. One
binary release for FreeBSD _and_ Linux?
Yes, and
Actually only a 4 years -- the a.out-ELF cut over broke the 5-10 years
of binary compatibility. As mentioned at
http://gcc.gnu.org/ml/gcc-patches/2002-01/msg01783.html we really made a
mistake when we did the a.out-ELF cut over thus resulting in us breaking
the i386 ELF ABI. I have
12MB? The last time I tried on a 16MB machine, it core dumped because
it ran out of memory. I had to put 24MB in the machine before it
would work (I couldn't try 20MB due to onhand SIMMs).
Uhh, I think we should move forward, like everyone else says. I mean, I
don't throw computers away,
On Sat, 26 Oct 2002, Julian Elischer wrote:
what would it take to allow burncd to work on SCSI devices.?
You got it backwards -- is atapicam complete enough to work reliably with
cdrecord?
I don't see why it shouldn't work on -CURRENT.
It works fine for me on -STABLE, for oh, months and
On Sat, Aug 31, 2002 at 00:04:44 +0200, Jens Schweikhardt wrote:
# and midnight commander shows all with -, +, | instead of
# pesudo-graphics.
It seems this is the price we pay for alignment with what XFree86 ships.
We don't need to pay, if entries will be _really_ corrected
IMHO, it has been corrected, and was incorrect before.
I mean, corrected for ACS characters (pseudo-graphics), which are correct
before. Read complains above.
I believe that these are fixed by not using an incorrect termtype (e.g.
'xterm-color', which refers to another terminal type
i'm trying to install current from cd (i took 3 different builds) to
my notebook hp omnibook 6100. by booting the kernel after few lines
is the machine crashing. i'm not abte to see the reason, everything
goes too fast. has anybody similar situation? any ideas why? 4.6
works fine.
Hi
Hi,
What's the status of the CAM/ATAPI integration? Is anyone thinking of
working on it?
When last mentioned, it was mooted that some work needed to be done to
tidy things up. Since then, it's gone very quiet - specifically, I don't
seem to recall seeing any specifics about what needed to
You'll be happy to tell them sys/dev/ata/atapi-cam.c:
Revision 1.1
Fri Aug 9 20:51:53 2002 UTC (3 days, 3 hours ago) by sos
Branch: MAIN
Well, golly...
And with improvements too! In good time for an MFC for 4.7! Awesome, no,
outstanding!
Thanks to all concerned, I really am very happy
Anybody have any idea what I need and where I can find it?
http://www.cuivre.fr.eu.org/~thomas/atapicam/
Just as a datapoint, I recently applied the ATAPI/CAM patches to a -STABLE
from July 10th).
They applied flawlessly, compile was clean.
My newly-acquired TEAC DW-28E CDR/CDRW/DVD
OK. Here we see the confluance of two problems. First, irq 0 is
bogus and likely illegal per the pci spec for devices that do
interrupt. Even if it isn't illegal, it is wrong wrong wrong wrong,
but lots of people do it. I have a patch for -stable, but not for
current.
Well, the card
Your message dated: Tue, 21 Mar 2000 20:57:17 GMT
Is this because xmcd needs updating to work with the new CAM system,
or something else?
You need to recompile xmcd.
In that case I need to wait for the package to be updated. xmcd needs
Motif, which I don't have, so I use the binary
Your message dated: Mon, 28 Feb 2000 23:49:07 EST
Will Andrews wrote:
One compatability problem would seem to be lack of support for the
Number Nine I128 board, previously supported in 3.3.*.
AOL
Me too! :-)
/AOL
This is very
disappointing, as I've got to use that board to drive my SGI
On Tue, Feb 22, 2000 at 03:46:04PM -0700, Kenneth D. Merry wrote:
On Tue, Feb 22, 2000 at 23:33:26 +0100, Jeroen Ruigrok van der Werven wrote:
-On [2222 23:25], Daniel O'Connor ([EMAIL PROTECTED]) wrote:
On 22-Feb-00 Jeroen Ruigrok van der Werven wrote:
Should be used instead.
I
On Fri, Jan 07, 2000 at 02:03:29AM +0100, Karsten W. Rohrbach wrote:
detection and removal (real goodd error correction) and this ones also
really fast (10x speed) when youre reading on a plextor drive (such as
my pxw4220t) or something else that has a native mode for extracting
audio.
One
16 matches
Mail list logo