Re: cvs commit: src/sys/sys select.h
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/libkvm_proc.c' does '#include sys/tty.h' which in turn has the line: #include sys/select.h /* For struct selinfo */ As a result 'make buildworld' stops in 'src/lib/libkvm'. N.Dudorov To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Kernel build failing in ip6_input.c
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 get the following:
...
cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi
-nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf
-mpreferred-stack-boundary=2 ../../netinet6/ip6_input.c
../../netinet6/ip6_input.c: In function `ip6_input':
../../netinet6/ip6_input.c:312: `inetsw' undeclared (first use in this
function)
../../netinet6/ip6_input.c:312: (Each undeclared identifier is reported only once
../../netinet6/ip6_input.c:312: for each function it appears in.)
../../netinet6/ip6_input.c:312: `ip_protox' undeclared (first use in this function)
*** Error code 1
snip
This error is generated that I use IPFILTER and INET6 with
configuration file.
This is my dirty hack.
This code does not do a check of action of IPv6.
--- ../ip6_input.c Mon Jul 31 22:11:42 2000
+++ ip6_input.c Sun Aug 6 16:39:33 2000
@@ -309,7 +309,7 @@
* in the list may have previously cleared it.
*/
m0 = m;
- pfh = pfil_hook_get(PFIL_IN, inetsw[ip_protox[IPPROTO_IPV6]].pr_pfh);
+ pfh = pfil_hook_get(PFIL_IN, inet6sw[ip6_protox[IPPROTO_IPV6]].pr_pfh);
for (; pfh; pfh = pfh-pfil_link.tqe_next)
if (pfh-pfil_func) {
rv = pfh-pfil_func(ip6, sizeof(*ip6),
--- ../ip6_output.c Mon Jul 31 22:11:42 2000
+++ ip6_output.cSun Aug 6 16:39:40 2000
@@ -110,6 +110,8 @@
#include netinet6/ip6_fw.h
#endif
+#include netinet6/ip6protosw.h
+
static MALLOC_DEFINE(M_IPMOPTS, "ip6_moptions", "internet multicast options");
struct ip6_exthdrs {
@@ -130,6 +132,9 @@
static int ip6_insert_jumboopt __P((struct ip6_exthdrs *, u_int32_t));
static int ip6_splithdr __P((struct mbuf *, struct ip6_exthdrs *));
+extern struct ip6protosw inet6sw[];
+extern u_char ip6_protox[IPPROTO_MAX];
+
/*
* IP6 output. The packet in mbuf chain m contains a skeletal IP6
* header (with pri, len, nxt, hlim, src, dst).
@@ -854,7 +859,7 @@
* Run through list of hooks for output packets.
*/
m1 = m;
- pfh = pfil_hook_get(PFIL_OUT, inetsw[ip_protox[IPPROTO_IPV6]].pr_pfh);
+ pfh = pfil_hook_get(PFIL_OUT, inet6sw[ip6_protox[IPPROTO_IPV6]].pr_pfh);
for (; pfh; pfh = pfh-pfil_link.tqe_next)
if (pfh-pfil_func) {
rv = pfh-pfil_func(ip6, sizeof(*ip6), ifp, 1, m1);
---
[EMAIL PROTECTED]
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Intel 815E chipset ATA100 tester wanted!!
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 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Failure build libkvm
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/lib/libkvm/kvm_proc.c -o kvm_proc.o In file included from /usr/src/lib/libkvm/kvm_proc.c:57: /usr/src/lib/libkvm/../../sys/sys/tty.h:84: field `t_rsel' has incomplete type /usr/src/lib/libkvm/../../sys/sys/tty.h:85: field `t_wsel' has incomplete type *** Error code 1 Maybe someone has an idea of what has happened recently. Unfortunately, (actually, for obscure reasons it is fortunately) I have to work on Sunday so I won't be able to investigate further. George Dinolt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/sys select.h
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/libkvm_proc.c' does '#include sys/tty.h' which in turn has the line: #include sys/select.h /* For struct selinfo */ As a result 'make buildworld' stops in 'src/lib/libkvm'. I knew something like this would happen and we'd catch some improperly written software. Thanks :) N.Dudorov -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / [EMAIL PROTECTED]`--' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[Neomagic] newpcm problems under current
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: NeoMagic 256AV at memory 0xfe00, 0xfea0 irq 9 (1p/1r channels duplex) 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... 404 [20:24] roberto@sidhe:~ mpg123 Lily_Was_Here.mp3 High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2 and 3. Version 0.59r (1999/Jun/15). Written and copyrights by Michael Hipp. Uses code from various people. See 'README' for more! THIS SOFTWARE COMES WITH ABSOLUTELY NO WARRANTY! USE AT YOUR OWN RISK! Can't open /dev/dsp! $FreeBSD: src/sys/dev/sound/pci/neomagic.c,v 1.13 2000/07/03 20:52:27 cg Exp $ $FreeBSD: src/sys/dev/sound/pci/neomagic.h,v 1.1 2000/01/09 08:14:11 cg Exp $ Any idea ? -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 CEST 2000 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
CFR: apm obtain per battery information
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 Aid Society Yokohama, Japan [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.imasy.org/~ume/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
HEADS UP! experimental ATA100 added..
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 on the promise and 50MB/s on the HPT370 so it seems writing is still done in ATA66 mode :( The ICH2 support is untested as of yet... Reports are very welcome! -Søren To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
vga0, atkbdc0, fdc0 attaching to ISA bus?
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. Specifically: pci0: SiS 5597/98 SVGA controller at 19.0 irq 11 The video controller is on the PCI. But vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 How can the VGA be ISA when the controller is on the PCI bus? Also, fdc0: NEC 72065B or clone at port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on isa0 atapci0: SiS 5591 ATA33 controller port 0xd000-0xd00f,0xd400-0xd403,0xd800-0xd807,0xe000-0xe003,0xe400-0xe407 irq 11 at device 1.1 on pci0 See how the floppy controller is on the ISA bus while the ATA driver is attaching to the PCI bus? Is there some bug in the bus probing routines? - Donn Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Thu Aug 3 10:05:18 EDT 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/CUSTOM Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 166450605 Hz CPU: Pentium/P55C (166.45-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping = 3 Features=0x8001bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX real memory = 62914560 (61440K bytes) avail memory = 57761792 (56408K bytes) Preloaded elf kernel "kernel" at 0xc037a000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc037a09c. Intel Pentium detected, installing workaround for F00F bug md0: Malloc disk npx0: math processor on motherboard npx0: INT 16 interface pcib0: Host to PCI bridge on motherboard pci0: PCI bus on pcib0 pci0: Host to PCI bridge (vendor=1039 device=5597) at 0.0 isab0: SiS 85c503 PCI-ISA bridge at device 1.0 on pci0 isa0: ISA bus on isab0 atapci0: SiS 5591 ATA33 controller port 0xd000-0xd00f,0xd400-0xd403,0xd800-0xd807,0xe000-0xe003,0xe400-0xe407 irq 11 at device 1.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ed0: NE2000 PCI Ethernet (RealTek 8029) port 0xb800-0xb81f irq 10 at device 10.0 on pci0 ed0: address 00:c0:df:ed:0b:17, type NE2000 (16 bit) pci0: SiS 5597/98 SVGA controller at 19.0 irq 11 sio2 at port 0x3e8-0x3ef irq 4 on isa0 sio2: type 16550A mse0: Bus/InPort Mouse at port 0x23c-0x23f irq 3 on isa0 sc0: System console on isa0 sc0: VGA 16 virtual consoles, flags=0x200 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sbc1: ESS ES1868 at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on isa0 pcm0: ESS 18xx DSP on sbc1 ppc0: ECP parallel printer port at port 0x378-0x37f,0x778-0x77f irq 7 drq 3 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold plip0: PLIP network interface on ppbus0 lpt0: Printer on ppbus0 lpt0: Interrupt-driven port ppi0: Parallel I/O on ppbus0 unknown: PNP0501 can't assign resources unknown: PNP0501 can't assign resources fdc0: NEC 72065B or clone at port 0x3f2-0x3f5,0x3f7 irq 6 drq 2 on isa0 atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 irq 1 on isa0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 ad0: 3093MB FUJITSU MPB3032ATU [6704/15/63] at ata0-master using UDMA33 ad1: 1040MB M1614TA [2114/16/63] at ata0-slave using WDMA2 acd0: CDROM BCD-24X 1997-06-27 at ata1-master using WDMA2
Breakage in emu10k1.c ver 1.13?
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_READADDRESS_MASK" there, but no "CCR_READADDRESS." -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://store.exit.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vga0, atkbdc0, fdc0 attaching to ISA bus?
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 internal ISA bus? Check out my dmesg. 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 obviously connected to the PCI bus. I suspect that some of these devices may be tied to the ISA bus in the BIOS for arcane PC/AT reasons. I would be interested to know details though, if someone could spare a moment to give an over-the-top explanation of why this is true. Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [Neomagic] newpcm problems under current
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 trap the lack of irqs and disable the channel and emit a warning to the console. access to hardware would make this easier to fix. -cg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Will the urio dev make it to -stable?
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 UHCI driver is needed to get performance up to reasonable levels (bandwidth reclamation). Nick On Sun, 16 Jul 2000, Frank Mayhar wrote: ...any time soon? It's been in current since 3/16 so it would seem MFCable, but what do I know. Nick? (I run 4-stable and don't plan to run -current any time soon, _and_ I want to buy a Rio 500, but not if I can't hook it to FreeBSD.) Sent to both -current and -stable as both lists seem relevant. Please limit followups, though. -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://store.exit.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message -- Qube Software, Ltd. Private: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.qubesoft.com/ http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [Neomagic] newpcm problems under current
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 do get lots of interrupt. I patched my kernel in June to generate a printf for each interrupt and I was seeing lots of them without even running mpg123. Aug 3 19:17:28 sidhe /kernel: getting an intr Aug 3 19:17:59 sidhe last message repeated 33 times Aug 3 19:18:57 sidhe last message repeated 73 times Aug 3 19:18:58 sidhe /kernel: getting an intr Aug 3 19:19:29 sidhe last message repeated 53 times Aug 3 19:20:37 sidhe last message repeated 93 times access to hardware would make this easier to fix. I would be difficult to send you my laptop, I do use it :-) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- [EMAIL PROTECTED] FreeBSD keltia.freenix.fr 5.0-CURRENT #80: Sun Jun 4 22:44:19 CEST 2000 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [Neomagic] newpcm problems under current
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 and emit a warning to the console. I do get lots of interrupt. I patched my kernel in June to generate a printf for each interrupt and I was seeing lots of them without even running mpg123. 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. access to hardware would make this easier to fix. I would be difficult to send you my laptop, I do use it :-) :) -cg To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vga0, atkbdc0, fdc0 attaching to ISA bus?
"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 all PCI slots, that there's still an internal ISA bus? Check out my dmesg. 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 obviously connected to the PCI bus. I suspect that some of these devices may be tied to the ISA bus in the BIOS for arcane PC/AT reasons. I would be interested to know details though, if someone could spare a moment to give an over-the-top explanation of why this is true. I'm working on a little util similar to pciconf -l right now.. but using a large array of vendor/device strings for the id's.. Does pciconf -l display those devices as being part of the PCI bus or are they out of the picture completely? -mike. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: if_tun.ko seems broken
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 thing here. It simply kldload()s the module, but you can't tell kldload() what interface you're interested in, therefore tunattach() just adds the devsw and leaves it at that, not if_attach()ing any specific interfaces. ifconfig then goes through the interfaces available and doesn't find what it was trying to load. I don't think it's right for ifconfig() to know any more, and I don't think kldload() should know anything about unit numbers, so this magic isn't really possible AFAICT. On Thu, 27 Jul 2000 09:37:11 +0200, Poul-Henning Kamp wrote: ifconfig tun0 inet 10.0.0.1 I think you are seing the "interesting" side effect of the BSD concept of "POINT2POINT" lines. I think that's anotehr issue. Once I'd read 0 bytes from /dev/tun0 with dd(1), I was able to do ifconfig tun0 inet 10.0.0.1 10.0.0.1 which is actually what I wanted. Ciao, Sheldon. -- Brian [EMAIL PROTECTED]brian@[uk.]FreeBSD.org http://www.Awfulhak.org brian@[uk.]OpenBSD.org Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/sys select.h
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 mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vga0, atkbdc0, fdc0 attaching to ISA bus?
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 obviously connected to the PCI bus. I suspect that some of : these devices may be tied to the ISA bus in the BIOS for arcane PC/AT : reasons. I would be interested to know details though, if someone could : spare a moment to give an over-the-top explanation of why this is true. Well, here's the short answer: 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, keyboard or mouse on the pci bus, but I'm sure people will tell me where I can find such beasts). Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vga0, atkbdc0, fdc0 attaching to ISA bus?
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, keyboard or mouse on the pci bus, : but I'm sure people will tell me where I can find such beasts). I should have also added: Even though there are no ISA expansion slots on your machine, you still have an ISA bus living inside (unless it is a legacy free machine we keep hearing about, which I didn't think was on the market). The PC-99 standard (not to be confused with the Japanese PC-98 machines) states that you cannot have a ISA expansion slot, but a later clarification to the standard states clearly that you can still have ISA devices built into the mother board. In other words, No ISA slots doesn't necessarily mean that the machine doesn't have an ISA bus. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/sys select.h
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 make buildworld first? 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 allowing "all" of the software to work, no matter how wrong it is. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / [EMAIL PROTECTED]`--' To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: cvs commit: src/sys/sys select.h
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 allowing "all" of the software to work, no matter how : wrong it is. I guess my point was rather aimed at saying "If you were going to make that change, you should have at least done a make buildworld to see what it would break and fixed that in the tree." Since you've reverted the change, I'll not worry about it further. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vga0, atkbdc0, fdc0 attaching to ISA bus?
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 hardware : designs (I've yet to see a floppy, keyboard or mouse on the pci bus, : but I'm sure people will tell me where I can find such beasts). I should have also added: Even though there are no ISA expansion slots on your machine, you still have an ISA bus living inside (unless it is a legacy free machine we keep hearing about, which I didn't think was on the market). The PC-99 standard (not to be confused with the Japanese PC-98 machines) states that you cannot have a ISA expansion slot, but a later clarification to the standard states clearly that you can still have ISA devices built into the mother board. In other words, No ISA slots doesn't necessarily mean that the machine doesn't have an ISA bus. 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 limitation reason for it. Otherwise it seems silly. =) Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vga0, atkbdc0, fdc0 attaching to ISA bus?
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 limitation reason for it. Otherwise it seems silly. =) If you can forget something, so can I. ;-) I should have added: vga0: S3 Trio graphics accelerator rev 0x00 int a irq 12 on pci0.16.0 vga0 at 0x3b0-0x3df maddr 0xa msize 131072 on isa ^ ^^^ That's what I'm talking about. Brandon D. Valentine -- bandix at looksharp.net | bandix at structbio.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vga0, atkbdc0, fdc0 attaching to ISA bus?
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 hardware : designs (I've yet to see a floppy, keyboard or mouse on the pci bus, : but I'm sure people will tell me where I can find such beasts). I should have also added: Even though there are no ISA expansion slots on your machine, you still have an ISA bus living inside (unless it is a legacy free machine we keep hearing about, which I didn't think was on the market). The PC-99 standard (not to be confused with the Japanese PC-98 machines) states that you cannot have a ISA expansion slot, but a later clarification to the standard states clearly that you can still have ISA devices built into the mother board. In other words, No ISA slots doesn't necessarily mean that the machine doesn't have an ISA bus. 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 limitation reason for it. Otherwise it seems silly. =) Brandon D. Valentine If you read the PCI's specification, video cards are given special treatment due to necessary backward compatibility with ISA video cards. PCI video cards occupies ISA bus resources (ports and memory range) and these are handled in a special manner which is not quite PCI bus's way. If a video card uses only PCI bus resources and does not occupy any of legacy ISA bus resoruces, it is indeed silly that it is recognized to be on the ISA bus. But, the reality is that the PCI video card is a half-PCI and half-ISA device... Kazu To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vga0, atkbdc0, fdc0 attaching to ISA bus?
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.vanderbilt.edu "Truth suffers from too much analysis." -- Ancient Fremen Saying To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: vga0, atkbdc0, fdc0 attaching to ISA bus?
: 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 front end that kicks the device into isa legacy mode. video is one (since it must support legacy things). pcic is another, because writing a native cardbus bridge code is a lot harder than writing a front end that kicks it into compat mode. but atakbdc and fdc, those really are isa devices. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
nullfs patch
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
