> From: attila! <[EMAIL PROTECTED]>
> Date: Sun, 6 Aug 2000 04:50:06 GMT
> on Sat, 5 Aug 2000 20:49:21 -0300 (ADT),
> Brandon Hume <[EMAIL PROTECTED]> wrote:
>
> > I went about a week without updating my source tree, but yesterday when I
> > went to build a kernel (and day), I
Well subject says it all, anybody with such a beast also called
ICH2 which is currently unsupported in -current
You need to have the 815E chipset and an ATA100 capable disk
to test out the code in question here..
Oh, and this _might_ cause trouble, so you have been warned :)
Thanks!
-Søren
Quick report:
I saw a failure building libkvm while trying to do a build world using
sources cvsuped aound 1.00 A.M. Pacific Daylight Time (U.S.) Sunday,
Aug 6. The error messages I saw were
cc -O -pipe -DLIBC_SCCS -I/usr/src/lib/libkvm/../../sys
-I/usr/obj/usr/src/i386/usr/include -c /usr/src/
On Sun, 6 Aug 2000, Nickolay Dudorov wrote:
> In article <[EMAIL PROTECTED]> you wrote:
> > green 2000/08/05 19:14:53 PDT
> >
> > Modified files:
> > sys/sys select.h
> > Log:
> > None of select.h needs to be exposed to !_KERNEL.
>
> But 'src/lib/lib/libkvm/l
FreeBSD sidhe.freenix.org 5.0-CURRENT FreeBSD 5.0-CURRENT #19: Thu Aug 3 19:19:36
CEST 2000 roberto@sidhe:/src/src/sys/compile/nSIDHE i386
FreeBSD Audio Driver (newpcm) Aug 3 2000 17:03:04
Installed devices:
pcm0: at memory 0xfe00, 0xfea0 irq 9 (1p/1r channels duplex)
The first
Hi,
I added output of per battery information to apm(1). To obtain this
information safely, I propose new ioctl APMIO_GETPWSTATUS.
http://www.imasy.or.jp/~ume/FreeBSD/apm-pwstatus.diff
If there is no objection, I'll commit this next week end.
Thanks,
--
Hajimu UMEMOTO @ Internet Mutual A
I've just committed support for the following ATA100 controllers:
Promise Ultra100 / Fasttrak100
HighPoint HPT370 controllers (fx Abit KA7-100 onboard ctrl, Abit HotRod 100)
Intel ICH2 (Intel 815E based motherboards)
So far I can read >90MB/s on the Promise and the HPT370.
I can write >64MB/s o
Anyone know why these devices want to attach to the ISA bus on a primarily
PCI bus machine? My MoBo is an Asus SP97-V, which has a mixture of ISA
and PCI slots. I was wondering maybe if even machines that have all PCI
slots, that there's still an internal ISA bus? Check out my dmesg.
Specifica
I saw Cameron's checkin and decided to try it out; I update to that
version of emu10k1.c, tried to build and got an undefined for
"CCR_READADDRESS." Grepping around, it doesn't seem to be defined
anywhere; I would expect to find it in gnu/dev/sound/pci/emu10k1.h
but no joy. There _is_ a "CCR_REA
On Sun, 6 Aug 2000, Donn Miller wrote:
>Anyone know why these devices want to attach to the ISA bus on a primarily
>PCI bus machine? My MoBo is an Asus SP97-V, which has a mixture of ISA
>and PCI slots. I was wondering maybe if even machines that have all PCI
>slots, that there's still an inter
> The first time I run mpg123, it does nothing (that is, no sound is
emitted)
> and afterwards, /dev/dsp can't be opened at all...
> Any idea ?
this is a known problem. it seems the neomagic driver never worked right,
so when newpcm became dependant on interrupts it ceased functioning. now we
t
Due to lack of time and other priorities I've not had a good look at the
driver for problems. I think that the initial submitter has a more
recent version available and that one should be tested. The NetBSD
version is also different and I need to look at what that one does.
Also, a patch to the
According to Cameron Grant:
> this is a known problem. it seems the neomagic driver never worked right,
Well, it used to work :)
> so when newpcm became dependant on interrupts it ceased functioning. now we
> trap the lack of irqs and disable the channel and emit a warning to the
> console.
I
> According to Cameron Grant:
> > this is a known problem. it seems the neomagic driver never worked
right,
> Well, it used to work :)
it used to *appear* to work.
> > so when newpcm became dependant on interrupts it ceased functioning.
now we
> > trap the lack of irqs and disable the channel a
On my -current box, buildworld failed as below.
===> libexec/telnetd
cc -g -DLINEMODE -DUSE_TERMIO -DDIAGNOSTICS -DOLD_ENVIRON -DENV_HACK
-I/usr/src/libexec/telnetd/../../lib -DINET6 -I/usr/obj/usr/src/i386/usr/include -c
/usr/src/libexec/telnetd/global.c
cc -g -DLINEMODE -DUSE_TERMIO -DDIA
"Brandon D. Valentine" wrote:
>
> On Sun, 6 Aug 2000, Donn Miller wrote:
>
> >Anyone know why these devices want to attach to the ISA bus on a primarily
> >PCI bus machine? My MoBo is an Asus SP97-V, which has a mixture of ISA
> >and PCI slots. I was wondering maybe if even machines that have
Sorry for the delay (I've been away for 2 weeks).
As Ben pointed out, the act of opening the /dev device is the key -
specifically, the if_attach() called from tuncreate() called from
tunopen() does some permanent damage^Wgood.
I don't think ifconfig really has a chance of doing the right thin
In message <[EMAIL PROTECTED]> Brian
Fundakowski Feldman writes:
: I knew something like this would happen and we'd catch some improperly
: written software. Thanks :)
No offense, but if you knew this was going to happen, why didn't you
do a make buildworld first?
Warner
To Unsubscribe: send
In message <[EMAIL PROTECTED]> "Brandon D.
Valentine" writes:
: I've got a machine with an Abit SL6 w/ AGP/PCI/CNR onboard, but no ISA
: slots, and it still has an ISA to PCI bridge built in. Some of the
: devices still register with the kernel on the ISA bus, even though they
: are quite obviou
In message <[EMAIL PROTECTED]> Warner Losh writes:
: The reason you have a ISA to PCI bridge still is that the serial
: ports, parallel ports, floppy, keyboard and mouse devices still live
: on the ISA bus. They aren't full PCI nodes just yet in most hardware
: designs (I've yet to see a floppy,
"me too"
pcm0: mem 0xfda0-0xfdaf,0xfac0-0xfaff irq
5 at device 0.1 on pci1
pcm0: play interrupt timeout, channel dead
Then EBUSY until the cows come home. I chatted with Cam some this
evening; this problem seems to have come about as a result of driver
restructuring. This chi
On Sun, 6 Aug 2000, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Brian
>Fundakowski Feldman writes:
> : I knew something like this would happen and we'd catch some improperly
> : written software. Thanks :)
>
> No offense, but if you knew this was going to happen, why didn't you
> do a
In message <[EMAIL PROTECTED]> Brian
Fundakowski Feldman writes:
: There are only three choices. One is to break some of the software.
: Another is to break some other amount of the software. The other is
: to make our headers even more totally horrid than they are now, but
: still tenuously al
On Sun, 6 Aug 2000, Warner Losh wrote:
>In message <[EMAIL PROTECTED]> Warner Losh writes:
>: The reason you have a ISA to PCI bridge still is that the serial
>: ports, parallel ports, floppy, keyboard and mouse devices still live
>: on the ISA bus. They aren't full PCI nodes just yet in most ha
On Mon, 7 Aug 2000, Brandon D. Valentine wrote:
>Well, I understand that, my question is, why are true PCI devices like
>video controllers still shown as being on isa0 by the kernel? I wanted
>an explanation of that. That's what doesn't make sense to me. Perhaps
>there's a valid PC/AT hardware
>On Sun, 6 Aug 2000, Warner Losh wrote:
>
>>In message <[EMAIL PROTECTED]> Warner Losh writes:
>>: The reason you have a ISA to PCI bridge still is that the serial
>>: ports, parallel ports, floppy, keyboard and mouse devices still live
>>: on the ISA bus. They aren't full PCI nodes just yet in m
On Mon, 7 Aug 2000, Kazutaka YOKOTA wrote:
>recognized to be on the ISA bus. But, the reality is that the PCI
>video card is a half-PCI and half-ISA device...
Thank you, Kazu. That sucks, but at least it makes sense now.
Brandon D. Valentine
--
bandix at looksharp.net | bandix at structbio
: >Well, I understand that, my question is, why are true PCI devices like
: >video controllers still shown as being on isa0 by the kernel?
Yokota-san's answer is correct here, which I've not repeated.
however, atkbdc0 is a isa device as is fdc0.
For some drivers it is easier to hack a pci fron
According to Cameron Grant:
> is the irq shared? have your printf display the neomagic status - i'll bet
> it's 0 indicating the irq was not generated by the neomagic.
Ahem, yes it is shared, by almost everything on the machine. Should have
thought of that...
--
Ollivier ROBERT -=- FreeBSD: Th
Hmmm. I'm seeing something like this. I have an
and mpg123 will play a list of songs correctly, but if I ^C out of it and
try again, I see the "pcm0: play interrupt timeout, channel dead" message
and it don't want to play again until a reboot.
The gusc0 device is the only one using irq 5 and I h
Hi!
Here is a patch, it seems it fix some bugs in nullfs.
At least i was able to make kernel on nullfs mounted
filesystem.
All results are welcome!
Good luck!
patch
31 matches
Mail list logo
