Re: newbus and modem(s)
Alex Zepeda wrote: On Sun, 18 Apr 1999, Brian Feldman wrote: I saw this and just had to note something to you. THINK what branch you are using. This is _WHERE_ things are being aired publically, and merged eventually to the STABLE branch. Gosh, thank you, without your wonderful help and understanding, I NEVER would have been able to realize this. You are so smart. Will you commit my code which breaks a few things and causes a panic? Wouldya? Huh? Huh? Huh? I think that what everyone is trying to say is that with CURRENT, about the best _guarantee_ you can get of a warning is Fire in the hole!!, with just about anything else a total freebie. If you don't like that, rather run STABLE. :-) M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
pcm sound driver crashes at boot time.
I haven't been able to track down exactly where this is occuring, but disabling pcm allows eliminates the crash. The build is current as of Sun 18th. The one strange thing about this box, it has two sounds cards. A build in Yamaha OPL-3 (really really crappy) and Ensoniq AudioPCI 1371 (very hacked driver, So the problem may be my fault). But I guessing it has more to do with the newbus stuff. disk1s3a: boot -cv BIOS basemem (639K) != RTC basemem (640K), setting to BIOS value Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #7: Sun Apr 18 16:48:43 CDT 1999 catte...@lupo.thebarn.com:/export/cyan/src/sys/compile/LUPO Calibrating clock(s) ... TSC clock: 333005093 Hz, i8254 clock: 1193009 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter i8254 frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium II/Xeon/Celeron (333.05-MHz 686-class CPU) Origin = GenuineIntel Id = 0x652 Stepping=2 Features=0x183fbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR real memory = 67108864 (65536K bytes) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x00306000 - 0x03ffdfff, 63930368 bytes (15608 pages) avail memory = 62156800 (60700K bytes) Found BIOS32 Service Directory header at 0xc00fdb60 Entry = 0xfdb70 (0xc00fdb70) Rev = 0 Len = 1 PCI BIOS entry at 0xdb91 DMI header at 0xc00f6ab0 Version 0.0 Table at 0xf6b8d, 32 entries, 999 bytes Other BIOS signatures found: ACPI: $PnP: 000f7a60 Preloaded elf kernel kernel at 0xc02f1000. Pentium Pro MTRR support enabled, default memory type is uncacheable Math emulator present Initializing PnP override table Probing for PnP devices: Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 PnP: CSN 1 COMP_DEVICE_ID = 0x2fb0d041 CSN 1 Vendor ID: YMH0802 [0x0208a865] Serial 0x Comp ID: PNPb02f [0x2fb0d041] Called nullpnp_probe with tag 0x0001, type 0x0208a865 Called nullpnp_probe with tag 0x0001, type 0x2fb0d041 pci_open(1):mode 1 addr port (0x0cf8) is 0x80003b40 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=71808086) pci_open(1):mode 1 addr port (0x0cf8) is 0x pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=71808086) npx0: math processor on motherboard npx0: INT 16 interface apm0: APM BIOS on motherboard apm: found APM BIOS version 1.2 pcib0: PCI host bus adapter on motherboard found- vendor=0x8086, dev=0x7180, revid=0x03 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[0]: type 3, range 32, base e000, size 28 found- vendor=0x8086, dev=0x7181, revid=0x03 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1secondarybus=1 found- vendor=0x8086, dev=0x7110, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 found- vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 map[0]: type 4, range 32, base ffa0, size 4 found- vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=d, irq=0 map[0]: type 4, range 32, base ef80, size 5 found- vendor=0x8086, dev=0x7113, revid=0x01 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 found- vendor=0x105d, dev=0x2339, revid=0x00 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=11 map[0]: type 3, range 32, base fd40, size 22 map[1]: type 3, range 32, base fd00, size 22 map[2]: type 1, range 32, base fe80, size 22 map[3]: type 1, range 32, base fe40, size 22 map[4]: type 1, range 32, base fe3f, size 16 map[5]: type 4, range 32, base ec00, size 8 found- vendor=0x10b7, dev=0x9055, revid=0x24 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=11 map[0]: type 4, range 32, base e480, size 7 map[1]: type 1, range 32, base fe3e6f80, size 7 found- vendor=0x1274, dev=0x1371, revid=0x02 class=04-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=11 map[0]: type 4, range 32, base ef00, size 6 found- vendor=0x9004, dev=0x7895, revid=0x03 class=01-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0secondarybus=0 intpin=a, irq=9 map[0]: type 4, range 32, base e000, size 8 map[1]: type 1, range 32, base
Re: newbus and modem(s)
On Mon, 19 Apr 1999 takaw...@shidahara1.planet.sci.kobe-u.ac.jp wrote: In message pine.bsf.3.96.990418205350.3261e-100...@heidi.plazza.it, Nick Hibm a wrote: Why would I say it wasn't ready? Because outside of core (apparently), nobody was warned/told that this was going to be committed in a few days/hours/minutes. I've ported the newconfig style USB code of NetBSD to FreeBSD and I really prefer the newbus style, because it is truly dynamic. Simple Question. If there were 'Closed'-Host-Controller-Interface with object-only driver, Can the vendor make the Host controller recognized without changing usb.c code? #That's what frustrated me while writing driver for smbus controller. It really depends on the nature of the bus. For plug-and-play style busses such as USB and PCI, the controller can decide what devices exist without the help of drivers and can then uniquely match them with the right driver. This trivially allows drivers to be added after the system is running. For 'manual' style busses, the creation of devices is generally controlled by hints. To create a new device for a new driver, it would be necessary to add the hint information for the new device and prompt the controller to add it. This isn't quite there yet but will be needed soon for dynamically adding devices (e.g. /usr/bin/joy). -- Doug Rabson Mail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: newbus and isa auto irq
On Sun, 18 Apr 1999, John Hay wrote:
Hi,
I ave found one more thing that seems to be broken. I have used the
irq autodetect feature of the ed(4) for a long time, but it seems
that the newbus compatability shim is not doing the right thing
with it. My kernel config file have a line like this:
device ed0 at isa? port 0x280 net irq ? iomem 0xd8000
The card gets probed but you just get device timeouts and there is no
mention of an irq for that device in the probe output. Booting with
-c and specifying the irq there also didn't work. Rebuilding the kernel
with a config file which specified the irq did work though.
Could you run a test kernel for me with this patch and tell me what it
prints.
Index: isa_compat.c
===
RCS file: /home/ncvs/src/sys/i386/isa/isa_compat.c,v
retrieving revision 1.3
diff -u -r1.3 isa_compat.c
--- isa_compat.c1999/04/19 08:42:39 1.3
+++ isa_compat.c1999/04/19 08:52:29
@@ -171,8 +171,11 @@
isa_set_portsize(dev, portsize);
if (dvp-id_iobase != isa_get_port(dev))
isa_set_port(dev, dvp-id_iobase);
- if (dvp-id_irq != (1 isa_get_irq(dev)))
+ if (dvp-id_irq != (1 isa_get_irq(dev))) {
+printf(isa_compat_probe: old irq=%d, new mask=%x, new irq=%d\n,
+ irq_get_irq(dev), dvp-id_irq, ffs(dvp-id_irq) - 1);
isa_set_irq(dev, ffs(dvp-id_irq) - 1);
+ }
if (dvp-id_drq != isa_get_drq(dev))
isa_set_drq(dev, dvp-id_drq);
if (dvp-id_maddr != maddr)
--
Doug Rabson Mail: d...@nlsystems.com
Nonlinear Systems Ltd. Phone: +44 181 442 9037
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: newbus and modem(s)
In message pine.bsf.4.05.9904190929070.85882-100...@herring.nlsystems.com, Do ug Rabson wrote: On Mon, 19 Apr 1999 takaw...@shidahara1.planet.sci.kobe-u.ac.jp wrote: Simple Question. If there were 'Closed'-Host-Controller-Interface with object-only driver, Can the vendor make the Host controller recognized without changing usb.c code? #That's what frustrated me while writing driver for smbus controller. It really depends on the nature of the bus. For plug-and-play style busses such as USB and PCI, the controller can decide what devices exist without the help of drivers and can then uniquely match them with the right driver. This trivially allows drivers to be added after the system is running. I don't mention on upstream driver such as 'ukbd' (I think such device can be add truly dynamic),but I mention on 'host-controller' like [ou]hci. What I ask is what shall I do if there is a downstream driver without declared DRIVER_MODULE on upstream bus.Are there any way without changing upstream bus code? Takanori Watanabe a href=http://www.planet.sci.kobe-u.ac.jp/~takawata/key.html; Public Key/a Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
imp Let us not forget that much of the newconfig work can be used with imp newconfig shims in the newbus scheme. If you are to construct a newconfig shim in the new-bus scheme, it means that you'll have two interface to device drivers. Then, you should consider, whether it is better to make a newconfig shim in the new-bus scheme than to make a new-bus shim in the newconfig scheme. By the way, how can I subscribe new-bus mailing list? It does not seem to be controlled by majord...@freebsd.org. Tomoaki Nishiyama e-mail:tomo...@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: newbus and modem(s)
On Mon, 19 Apr 1999, Takanori Watanabe wrote: In message pine.bsf.4.05.9904190929070.85882-100...@herring.nlsystems.com, Do ug Rabson wrote: On Mon, 19 Apr 1999 takaw...@shidahara1.planet.sci.kobe-u.ac.jp wrote: Simple Question. If there were 'Closed'-Host-Controller-Interface with object-only driver, Can the vendor make the Host controller recognized without changing usb.c code? #That's what frustrated me while writing driver for smbus controller. It really depends on the nature of the bus. For plug-and-play style busses such as USB and PCI, the controller can decide what devices exist without the help of drivers and can then uniquely match them with the right driver. This trivially allows drivers to be added after the system is running. I don't mention on upstream driver such as 'ukbd' (I think such device can be add truly dynamic),but I mention on 'host-controller' like [ou]hci. What I ask is what shall I do if there is a downstream driver without declared DRIVER_MODULE on upstream bus.Are there any way without changing upstream bus code? I don't think I understand. The DRIVER_MODULE declaration goes in the downstream driver, not the upstream bus. The bus doesn't need any knowledge of what drivers might be attached to it. -- Doug Rabson Mail: d...@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
jkh I don't go to new-bus, this direction is disunion of BSDs. It is jkh bad decision. jkh jkh I'm sorry that you feel this way, but I can only re-state that better jkh communication could have prevented this in the first place and hope jkh that you've learned your own lessons from this exercise. If you jkh haven't, then a good opportunity for learning has simply been wasted. One problem on the decision is that it was not based on a judge that new-bus is technically or philosophically superior to newconfig framework but you stated jkh the difference with new-bus being jkh that we were working just that much more closely with Doug Rabson (and jkh the others helping him) and had already used the new-bus stuff for jkh FreeBSD/alpha. Nakagawa would not be so upset if you could convince him that new-bus were superior. Tomoaki Nishiyama e-mail:tomo...@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: newbus and modem(s)
Simple Question. If there were 'Closed'-Host-Controller-Interface with object-only driver, Can the vendor make the Host controller recognized without changing usb.c code? If he exports a USB bus with the appropriate methods, he will be able to drop it in, yes. You might have noticed when installing USB support that you get a uhci0, usb0 and uhub0 device, basically all related to that one 82371AB chip that is on your motherboard. The problem currently is that, because of the porting of the NetBSD USB code, we use a mixed scheme, which makes things slightly more complicated. There is a separate method export mechanism for the UHCI/OHCI controllers. The way this is implemented currently in the NetBSD code is ugly, to say the least. #That's what frustrated me while writing driver for smbus controller. That is more of a design issue than something caused by newbus... Nick To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
new kernel and IPDIVERT
i have compiled the latest kernel and encountered a problem with IPDIVERT. even with options IPDIVERT string in kernel config, kernel says the following: IP packet filtering initialized, divert disabled, rule-based forwarding disabled, logging disabled of course, firewall rules like add divert natd ... do not work. everything is ok with old kernel (~5 days old). could anyone comment this? -- sincerely, ilya naumov (at work) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
One problem on the decision is that it was not based on a judge that new-bus is technically or philosophically superior to newconfig framework but you stated I don't think they're so far apart that there's a clear superiority, and we certainly didn't get that impression from any of the discussions we saw between you guys and the new-bus folks. All I saw were some strong differences of opinion being expressed and a good chance that superiority would never be objectively determined by any of the parties involved. Nakagawa would not be so upset if you could convince him that new-bus were superior. Again, this appeared to be a matter of fierce argument more than anything else and I'd probably be just as inclined to try and get a Mercedes owner to agree that BMW made a superior car when, in fact, both vehicles provide a more than adequate ride and have a number of nice features. Given that neither system is exactly standing still, it also meant that relative superiority was a constantly changing factor and even though it might have been possible to say that newconfig was superior on one month, it would be by no means assured that this would remain a constant. What it ultimately came down to, as I said before, was choosing the group we had the best communication with and had some existing precedent, in new-bus's case that being FreeBSD/alpha. We learned a lot of painful lessons from the PAO project given the difficulties we've had with integrating that technology on an ongoing basis, and those are lessons we had no wish to learn again. Judging superiority is only partially a technical issue, and there are many other factors of equal importance when you start discussing projects of long-term significance to FreeBSD. - Jordan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: newbus and isa auto irq
Hi,
I ave found one more thing that seems to be broken. I have used the
irq autodetect feature of the ed(4) for a long time, but it seems
that the newbus compatability shim is not doing the right thing
with it. My kernel config file have a line like this:
device ed0 at isa? port 0x280 net irq ? iomem 0xd8000
The card gets probed but you just get device timeouts and there is no
mention of an irq for that device in the probe output. Booting with
-c and specifying the irq there also didn't work. Rebuilding the kernel
with a config file which specified the irq did work though.
John
--
John Hay -- john@mikom.csir.co.za
I had the same problem. Here's a fix:
Index: isa_compat.c
===
RCS file: /home/ncvs/src/sys/i386/isa/isa_compat.c,v
retrieving revision 1.3
diff -u -r1.3 isa_compat.c
--- isa_compat.c1999/04/19 08:42:39 1.3
+++ isa_compat.c1999/04/19 10:07:41
@@ -131,12 +131,14 @@
}
}
+#defineirqmask(x) ((x) 0 ? 0 : (1 (x)))
+
static int
isa_compat_probe(device_t dev)
{
struct isa_device *dvp = device_get_softc(dev);
struct isa_compat_resources res;
-
+
bzero(res, sizeof(res));
/*
* Fill in the isa_device fields.
@@ -144,7 +146,7 @@
dvp-id_id = isa_compat_nextid();
dvp-id_driver = device_get_driver(dev)-priv;
dvp-id_iobase = isa_get_port(dev);
- dvp-id_irq = (1 isa_get_irq(dev));
+ dvp-id_irq = irqmask(isa_get_irq(dev));
dvp-id_drq = isa_get_drq(dev);
dvp-id_maddr = (void *)isa_get_maddr(dev);
dvp-id_msize = isa_get_msize(dev);
@@ -171,7 +173,7 @@
isa_set_portsize(dev, portsize);
if (dvp-id_iobase != isa_get_port(dev))
isa_set_port(dev, dvp-id_iobase);
- if (dvp-id_irq != (1 isa_get_irq(dev)))
+ if (dvp-id_irq != irqmask(isa_get_irq(dev)))
isa_set_irq(dev, ffs(dvp-id_irq) - 1);
if (dvp-id_drq != isa_get_drq(dev))
isa_set_drq(dev, dvp-id_drq);
-lq
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: new kernel and IPDIVERT
On Mon, 19 Apr 1999, Ilya Naumov wrote: i have compiled the latest kernel and encountered a problem with IPDIVERT. even with options IPDIVERT string in kernel config, kernel says the following: IP packet filtering initialized, divert disabled, rule-based forwarding disabled, logging disabled That's because it's loading the ipfw.ko KLD. of course, firewall rules like add divert natd ... do not work. everything is ok with old kernel (~5 days old). could anyone comment this? I know about it, but don't know how to fix it :( However, for now, you can go over to /usr/src/sys/modules/, edit the Makefile and add what features you want to CFLAGS, and make depend all install clean shutdown -r now. -- sincerely, ilya naumov (at work) To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message Brian Feldman_ __ ___ ___ ___ ___ gr...@unixhelp.org_ __ ___ | _ ) __| \ FreeBSD: The Power to Serve! _ __ | _ \ _ \ |) | http://www.freebsd.org _ |___)___/___/ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: newbus and modem(s)
Doug Rabson wrote: On Mon, 19 Apr 1999, Takanori Watanabe wrote: In message pine.bsf.4.05.9904190929070.85882-100...@herring.nlsystems.com , Do ug Rabson wrote: On Mon, 19 Apr 1999 takaw...@shidahara1.planet.sci.kobe-u.ac.jp wrote: Simple Question. If there were 'Closed'-Host-Controller-Interface with object-only driver , Can the vendor make the Host controller recognized without changing usb.c code? #That's what frustrated me while writing driver for smbus controller. It really depends on the nature of the bus. For plug-and-play style busses such as USB and PCI, the controller can decide what devices exist without the help of drivers and can then uniquely match them with the right driver. This trivially allows drivers to be added after the system is running. I don't mention on upstream driver such as 'ukbd' (I think such device can be add truly dynamic),but I mention on 'host-controller' like [ou]hci. What I ask is what shall I do if there is a downstream driver without declared DRIVER_MODULE on upstream bus.Are there any way without changing upstream bus code? I don't think I understand. The DRIVER_MODULE declaration goes in the downstream driver, not the upstream bus. The bus doesn't need any knowledge of what drivers might be attached to it. Well, what about the i386 nexus? It specifically creates connection points for apm, npx, eisa, isa, and pci as children. However, pci devices don't do this to attach to their parent. I am obviously missing something. :-) Cheers, -Peter To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: new kernel and IPDIVERT
Brian Feldman wrote: On Mon, 19 Apr 1999, Ilya Naumov wrote: i have compiled the latest kernel and encountered a problem with IPDIVERT. even with options IPDIVERT string in kernel config, kernel says the following: IP packet filtering initialized, divert disabled, rule-based forwarding dis abled, logging disabled That's because it's loading the ipfw.ko KLD. of course, firewall rules like add divert natd ... do not work. everythin g is ok with old kernel (~5 days old). could anyone comment this? I know about it, but don't know how to fix it :( However, for now, you can go over to /usr/src/sys/modules/, edit the Makefile and add what features you want to CFLAGS, and make depend all install clean shutdown -r now. It's quite likely I broke something with the LKM cleanup.. :-( I have not yet had a chance to revisit this, but will in a few hours. Cheers, -Peter To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: newbus and modem(s)
Let me try to post an example to see whether I understood your question: Let's assume we have a motherboard with an ISA NHCI (new host controller interface) apart from the standard PCI UHCI (Universal Host Controller Interface, Intel) available in the 82371AB chipset. We boot the system, the UHCI controller is recognised by the PCI bus driver (nexus - pci), probed by the UHCI driver (pci - usb) and this will create a driver that implements a usb devclass. It then starts a probe for devices on the bus it represents. The usb class driver was compiled into the kernel and attaches to that bus. This is the uhub driver (usb - uhub). You start websurfing and find this driver for your NHCI controller (New Host Controller Interface). After download you load the driver with kldload. The ISA bus is notified of the presence of a new driver and reprobes the ISA devices that are not attached by a driver. It probes the physical NHCI device with the NHCI driver (isa - usb) (succeeds) and attaches the loaded driver to it. This will create a new bus with device class usb. After the attach has finished, the probe_and_attach function is called and a usb class driver will probe and attach to this new bus. You now have two USB busses (the diagram contains 2 mice, 2 keyboards, 1 Zip drive, and 2 external and 2 root hubs): pci - usb - uhub - uhub - ums \ ukbd \ umass (Zip drive) \ usb - uhub - ums \ uhub - ukbd \ trackball (The '-' and '\' represent the spots where the drivers are located. The names represent the device classes). The usb class driver is able to talk to the UHCI or NHCI driver through predefined methods, like USB_DEVICE_BULK_TRANSFER, USB_DEVICE_BULK_TRANSFER_ABORT, USB_HOST_RESET, USB_HOST_SUSPEND, etc. In later releases methods can be added by using new names. What is not possible with newbus is to attach a pci - usb driver to a bus that is not called pci, but for example pci2. But this is a logical limitation as with the change of name for the bus, the interface to the bus must have changed as well. The devclass names should therefore not contain vendor, device or type specific interfaces, only generic interfaces. I hope this serves as an explanation for your question. Kind regards, Nick P.S.: Above is a wanted situation for the USB stack not the current. The current source code contains a more complicated approach due to the fact that it is converted from newconfig in NetBSD. The UHCI driver attaches to pci and creates one child for the usb bus. This could be removed. (e.g. pci - uhci - usb - uhub - ums, for a system with only a mouse attached). Second, the uhub driver is available in two device classes, usb and uhub. I don't mention on upstream driver such as 'ukbd' (I think such device can be add truly dynamic),but I mention on 'host-controller' like [ou]hci. What I ask is what shall I do if there is a downstream driver without declared DRIVER_MODULE on upstream bus.Are there any way without changing upstream bus code? Takanori Watanabe a href=http://www.planet.sci.kobe-u.ac.jp/~takawata/key.html; Public Key/a Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: newbus and modem(s)
Peter Wemm wrote: Doug Rabson wrote: On Mon, 19 Apr 1999, Takanori Watanabe wrote: In message pine.bsf.4.05.9904190929070.85882-100...@herring.nlsystems.co m , Do ug Rabson wrote: On Mon, 19 Apr 1999 takaw...@shidahara1.planet.sci.kobe-u.ac.jp wrote: Simple Question. If there were 'Closed'-Host-Controller-Interface with object-only driv er , Can the vendor make the Host controller recognized without changing usb.c code? #That's what frustrated me while writing driver for smbus controller. It really depends on the nature of the bus. For plug-and-play style buss es such as USB and PCI, the controller can decide what devices exist withou t the help of drivers and can then uniquely match them with the right driver. This trivially allows drivers to be added after the system is running. I don't mention on upstream driver such as 'ukbd' (I think such device can be add truly dynamic),but I mention on 'host-controller' like [ou]hci. What I ask is what shall I do if there is a downstream driver without declared DRIVER_MODULE on upstream bus.Are there any way without changing upstream bus code? I don't think I understand. The DRIVER_MODULE declaration goes in the downstream driver, not the upstream bus. The bus doesn't need any knowledge of what drivers might be attached to it. Well, what about the i386 nexus? It specifically creates connection points for apm, npx, eisa, isa, and pci as children. However, pci devices don't do this to attach to their parent. I am obviously missing something. :-) Never mind, I understand now. :-) For the benefit of the 'cc' list, and to check my understanding, let me run through it.. The parents pick up the children in one of two ways. For a 'smart' bus, like pci, usb, eisa, etc, the bus probes itself and adds an unidentified child (NULL name, -1 unit) with the known ID. The bus mechanism then uses this to poll the drivers to see which one(s) want to claim that ID. It knows who the children are because of the DECLARE_MODULE() statement. This means that a smart (or self identifying) bus doesn't need anything more to manage the relationship. On the other hand, there's isa, which is quite dumb. In this case, the bus looks up it's hint list and specifically adds the requested children from those hints, and using the supplied irq, port, etc values from the hints. The drivers then use that data to probe for the existance of the device. The nexus is a little bit different.. It doesn't have things to specifically look for, so it adds the children manually. It could have used the resource database to find the requested things to attach to the nexus in pretty much the same way as the isa bus does. And then there's the old isa drivers... They attach themselves to the isa parent device class on the fly, there is no DECLARE_MODULE() table for all the old isa (and perhaps PCI too) drivers. Doug, is that right so far? :-) Now what I'm curious about is how to handle the nexus and isa/eisa better so they don't need to explicitly name the children. On one hand it could look at the hints table to see all the 'at nexus?' declarations, but I think it might be better to go for a hunt to locate all the children it can find. One way to do this might be to simply add a heap of unidentified devices and let the bus mechanism find all the devices that are children and let them probe themselves while ignoring the fake device id's. Perhaps this could change the probe order enough so that isa and eisa won't be attached until after pci has been recursively probed. Cheers, -Peter To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: newbus and modem(s)
In message 19990419124505.62d951...@spinner.netplex.com.au, Peter Wemm wrote: Never mind, I understand now. :-) Ok, I think I also understand. The DRIVER_MODULE() macro is consist for static configuration to kick module initialization routine for every driver.Is it correct? But are ther more better way? Takanori Watanabe a href=http://www.planet.sci.kobe-u.ac.jp/~takawata/key.html; Public Key/a Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
error building kernel
I followed the instructions about NEXUS to rebuild my kernel, and it now it won't compile. It gets all the way through the compile, and then gives these errors. generating linker set emulation glue for ELF cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing -prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -no stdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_glob al.h -elf setdef0.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing -prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -no stdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_glob al.h -elf vnode_if.c cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing -prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -no stdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_glob al.h -elf ioconf.c ioconf.c:108: warning: `psm0_count' redefined ioconf.c:68: warning: this is the location of the previous definition ioconf.c:102: redefinition of `psm0_resources' ioconf.c:64: `psm0_resources' ioconf.c:64: `psm0_resources' previously defined here ioconf.c:105: warning: excess elements in array initializer after `psm0_resource s' ioconf.c:106: warning: excess elements in array initializer after `psm0_resource s' *** Error code 1 Stop. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: error building kernel
Kenneth Wayne Culver wrote: I followed the instructions about NEXUS to rebuild my kernel, and it now it won't compile. It gets all the way through the compile, and then gives these errors. I'll bet you've got two 'psm0' lines in the config file.. All that config is doing now is basically compiling a table of what's in your config file and saving that for the probe code to use. Yes, It should probably check for duplicates.. :-) al.h -elf ioconf.c ioconf.c:108: warning: `psm0_count' redefined ioconf.c:68: warning: this is the location of the previous definition ioconf.c:102: redefinition of `psm0_resources' ioconf.c:64: `psm0_resources' ioconf.c:64: `psm0_resources' previously defined here ioconf.c:105: warning: excess elements in array initializer after `psm0_resource s' ioconf.c:106: warning: excess elements in array initializer after `psm0_resource s' Cheers, -Peter To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
sysinstall crash system after cvsup at 990417
I supped my system at 990417. Then I make world and rebuild sysinstall. The command /stand/sysinstall crash my system during probe hard disk. Fatal trap 12: page fault while in kernel mode fault virtual address = 0x31 fault code = supervisor read, page not present instruction pointer = 0x8:0xc0136de0 stack pointer = 0x10:0xc4a03d98 frame pointer = 0x10:0xc4a03d98 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= interrupt enabled, resume, IOPL=0 current process = 2266 (sysinstall) interrupt mask = trap number = 12 panic: page fault To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: newbus and modem(s)
And then what about newconfig? To me this just adds more truth to the whole /. argument that *BSD promotes a closed development model. It's a flawed argument and one that doesn't acknowledge, at least in the case of FreeBSD, the existence of publicly accessible CVS repositories along with the GNATS databases for non-committer submissions. It's a more centralized development model but not necessarily a closed one. Cheers, Jerry Hicks wghi...@bellsouth.net To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: newbus and modem(s)
I saw this and just had to note something to you. THINK what branch you are using. This is _WHERE_ things are being aired publically, and merged eventually to the STABLE branch. Gosh, thank you, without your wonderful help and understanding, I NEVER would have been able to realize this. You are so smart. Will you commit my code which breaks a few things and causes a panic? Wouldya? Huh? Huh? Huh? Don't forget that the GNATS database is a wonderful resource for acquiring patches and submitting things experimental and/or broken for consideration by others. Cheers, Jerry Hicks wghi...@bellsouth.net To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: newbus and modem(s)
FreeBSD is somewhat of a closed development enviroment what some organizations do is that they maintain their own cvs repository. CVS repository is guarded by the core members and only certified committers are allowed to commit code that in addition to not having a procedure or a processs to mitigate technical conflicts such as new config vs new-bus makes the develpment process at least a closed one from the perspective of the FreeBSD cvs repository. And then what about newconfig? To me this just adds more truth to the whole /. argument that *BSD promotes a closed development model. It's a flawed argument and one that doesn't acknowledge, at least in the case of FreeBSD, the existence of publicly accessible CVS repositories along with the GNATS databases for non-committer submissions. It's a more centralized development model but not necessarily a closed one. Cheers, Jerry Hicks wghi...@bellsouth.net To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message -- Amancio Hasty ha...@star-gate.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: newbus and modem(s)
FreeBSD is somewhat of a closed development enviroment what some organizations do is that they maintain their own cvs repository. FreeBSD is no more closed than linux is, which is touted as the most open development project that exists. Joe Average person can no more commit can't commit code to the linux 'development' tree than he can to the FreeBSD tree, since there are 'developers' that maintain both trees. I know of *NO* completey open development environment, but FreeBSD's is *MUCH* more open than most, including Linux's. With the FreeBSD environment, the entire 'process' of development is more open (it is almost completely public except for some discussions that happen on the core mailing list, which I assume are less technical and more political) than any other project I'm aware of. What other project (aside from OpenBSD) gives you the ability to see the entire source code history of the tree, along with real-time discussion and development of the source code? All 'source code' control is guarded by a certain group of people in *every* project, and FreeBSD is no different. It just has different folks guarding it, who have different standards and requirements. Nate To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: newbus and modem(s)
Hi: Just wanted to say that I think the lack of a free-for-all CVS is exactly what is required to consistently move FreeBSD forward. If someone feels they would like to take a different approach, then I say by all means do so. If you can convince people to join your development effort then great!, if not, then great!. Rick Whitesel Scientist NBase-Xyplex rwhite...@nbase-xyplex.com They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin, 1759 - Original Message - From: W Gerald Hicks wghi...@bellsouth.net To: Alex Zepeda garba...@hooked.net Cc: Brian Feldman gr...@unixhelp.org; Daniel C. Sobral d...@newsguy.com; Jordan K. Hubbard j...@zippy.cdrom.com; current curr...@freebsd.org; wghi...@wghicks.bellsouth.net Sent: Monday, April 19, 1999 12:56 PM Subject: Re: newbus and modem(s) I saw this and just had to note something to you. THINK what branch you are using. This is _WHERE_ things are being aired publically, and merged eventually to the STABLE branch. Gosh, thank you, without your wonderful help and understanding, I NEVER would have been able to realize this. You are so smart. Will you commit my code which breaks a few things and causes a panic? Wouldya? Huh? Huh? Huh? Don't forget that the GNATS database is a wonderful resource for acquiring patches and submitting things experimental and/or broken for consideration by others. Cheers, Jerry Hicks wghi...@bellsouth.net To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: Important instructions for -current users!
On Mon, 19 Apr 1999 18:17:05 +0900, Tomoaki NISHIYAMA wrote: By the way, how can I subscribe new-bus mailing list? It does not seem to be controlled by majord...@freebsd.org. I took HEADS UP out of the Subject to help the guy who maintains src/UPDATING . :-) You can subscribe to the list by mailing majord...@bostonradio.org with no subject and the request subscribe new-bus-arch in the body of your message. Ciao, Sheldon. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: newbus and modem(s)
All 'source code' control is guarded by a certain group of people in *every* project, and FreeBSD is no different. It just has different folks guarding it, who have different standards and requirements. Perhaps a good step towards understanding would be if those guarding the process would actually state what is their standard and requirements, if they have any. It coud start by something like this: FreeBSD Development Guidelines and Motivation... It don't matter nothing has bee resolved with this issue for the last year when I highlighted this problem and I doubt that anything will come out of it this time. Time To Hack! 8) -- Amancio Hasty ha...@star-gate.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: newbus and isa auto irq
I ave found one more thing that seems to be broken. I have used the
irq autodetect feature of the ed(4) for a long time, but it seems
that the newbus compatability shim is not doing the right thing
with it. My kernel config file have a line like this:
device ed0 at isa? port 0x280 net irq ? iomem 0xd8000
The card gets probed but you just get device timeouts and there is no
mention of an irq for that device in the probe output. Booting with
-c and specifying the irq there also didn't work. Rebuilding the kernel
with a config file which specified the irq did work though.
Could you run a test kernel for me with this patch and tell me what it
prints.
It doesn't print anything for the ed0 device. It does print 2 lines though,
one for wdc0 and one for the printer port:
---
Apr 19 19:22:27 orca /kernel.doug: fdc0: FIFO enabled, 8 bytes threshold
Apr 19 19:22:27 orca /kernel.doug: fd0: 1440-KB 3.5 drive at fdc0 drive 0
Apr 19 19:22:27 orca /kernel.doug: isa_compat_probe: old irq=-1, new mask=4000,
new irq=14
Apr 19 19:22:27 orca /kernel.doug: wdc0 at port 0x1f0-0x1f7 irq 14 on isa0
Apr 19 19:22:27 orca /kernel.doug: wdc0: unit 0 (wd0): WDC AC2635F
Apr 19 19:22:27 orca /kernel.doug: wd0: 610MB (1249920 sectors), 1240 cyls, 16 h
eads, 63 S/T, 512 B/S
Apr 19 19:22:27 orca /kernel.doug: wdc0: interrupting at irq 14
...
Apr 19 19:22:28 orca /kernel.doug: isa_compat_probe: old irq=-1, new mask=80,
new irq=7
Apr 19 19:22:28 orca /kernel.doug: ppc0 at port 0x378 irq 7 on isa0
Apr 19 19:22:28 orca /kernel.doug: ppc0: SMC FDC37C665GT chipset (PS2/NIBBLE)
in COMPATIBLE mode
Apr 19 19:22:28 orca /kernel.doug: ppb0: IEEE1284 device found
Apr 19 19:22:28 orca /kernel.doug: Probing for PnP devices on ppbus0:
Apr 19 19:22:28 orca /kernel.doug: lpt0: generic printer on ppbus 0
Apr 19 19:22:28 orca /kernel.doug: lpt0: Interrupt-driven port
Apr 19 19:22:28 orca /kernel.doug: ppc0: interrupting at irq 7
Apr 19 19:22:28 orca /kernel.doug: ed0 at port 0x280-0x29f on isa0
Apr 19 19:22:28 orca /kernel.doug: ed0: address 00:00:c0:1d:43:db, type SMC8216/
SMC8216C (16 bit)
Apr 19 19:22:28 orca /kernel.doug: Intel Pentium detected, installing workaround
for F00F bug
- if (dvp-id_irq != (1 isa_get_irq(dev)))
+ if (dvp-id_irq != (1 isa_get_irq(dev))) {
+printf(isa_compat_probe: old irq=%d, new mask=%x, new irq=%d\n,
+ irq_get_irq(dev), dvp-id_irq, ffs(dvp-id_irq) - 1);
isa_set_irq(dev, ffs(dvp-id_irq) - 1);
+ }
I assume the irq_get_irq() should be isa_get_irq().
I have tried the patch that Luoqi posted and that works for me. Although
even with that the the userconfig by booting with -c don't work. It just
plain ignores what you do there.
John
--
John Hay -- john@mikom.csir.co.za
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
subscribe
subscribe To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: newbus and isa auto irq
John Hay wrote:
[..]
Apr 19 19:22:28 orca /kernel.doug: ppc0: interrupting at irq 7
Apr 19 19:22:28 orca /kernel.doug: ed0 at port 0x280-0x29f on isa0
Apr 19 19:22:28 orca /kernel.doug: ed0: address 00:00:c0:1d:43:db, type SMC82
16/
SMC8216C (16 bit)
Apr 19 19:22:28 orca /kernel.doug: Intel Pentium detected, installing workaro
und
for F00F bug
- if (dvp-id_irq != (1 isa_get_irq(dev)))
+ if (dvp-id_irq != (1 isa_get_irq(dev))) {
+printf(isa_compat_probe: old irq=%d, new mask=%x, new irq=%d\n,
+ irq_get_irq(dev), dvp-id_irq, ffs(dvp-id_irq) - 1);
isa_set_irq(dev, ffs(dvp-id_irq) - 1);
+ }
I assume the irq_get_irq() should be isa_get_irq().
I have tried the patch that Luoqi posted and that works for me. Although
even with that the the userconfig by booting with -c don't work. It just
plain ignores what you do there.
An additional datapoint... We have:
dvp-id_maddr = (void *)isa_get_maddr(dev);
[..]
void *maddr;
isa_compat_alloc_resources(dev, res);
if (res.memory)
maddr = rman_get_virtual(res.memory);
else
maddr = 0;
dvp-id_maddr = maddr;
portsize = dvp-id_driver-probe(dvp);
isa_compat_release_resources(dev, res);
if (portsize != 0) {
if (portsize 0)
isa_set_portsize(dev, portsize);
if (dvp-id_iobase != isa_get_port(dev))
isa_set_port(dev, dvp-id_iobase);
if (dvp-id_irq != (1 isa_get_irq(dev)))
isa_set_irq(dev, ffs(dvp-id_irq) - 1);
if (dvp-id_drq != isa_get_drq(dev))
isa_set_drq(dev, dvp-id_drq);
if (dvp-id_maddr != maddr)
isa_set_maddr(dev,
(int) dvp-id_maddr - KERNBASE);
^^
if (dvp-id_msize != isa_get_msize(dev))
isa_set_msize(dev, dvp-id_msize);
There is the problem.. isa_compat_release_resources() is clearing the
hints. The only reason it works for the other devices is things like:
if (dvp-id_iobase != isa_get_port(dev))
isa_set_port(dev, dvp-id_iobase);
.. ie: if (id_iobase != freshly cleared value)
reset_hint(id_iobase);
.. etc.
This is not happening for the maddr stuff.
I suspect this would do better:
if (portsize 0)
isa_set_portsize(dev, portsize);
if (dvp-id_iobase = 0)
isa_set_port(dev, dvp-id_iobase);
if (dvp-id_irq != 0)
isa_set_irq(dev, ffs(dvp-id_irq) - 1);
if (dvp-id_drq != -1)
isa_set_drq(dev, dvp-id_drq);
if (dvp-id_maddr != 0)
isa_set_maddr(dev,
(int) dvp-id_maddr - KERNBASE);
if (dvp-id_msize != 0)
isa_set_msize(dev, dvp-id_msize);
I'm not sure about the nothing value for id_drq though, it might need to
be 0 - but that's a valid dma channel.
IMHO, isa_release_resources() clearing of the default values for the probe
hints is a timebomb... I thought about adding a seperate store for the
hint values rather than using the id_foo[0] entries, and leaving the
tracked resource entries for alloc/free without risking the hints.
Cheers,
-Peter
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
Re: Language barrier (was Re: HEADS UP!!!! Important instructions for -current users! )
As Warner Losh wrote ... In message 199904181923.naa25...@mt.sri.com Nate Williams writes: : This is wonderful, but has this ever happened in our mailing lists? I : guess I don't remember anyone *ever* ridiculing or harassing someone for : not being fluent in the language. I have seen people ask others to explain again since they didn't understand, but I cannot recall ever seeing anybody holding someone up to ridicule publically. I have deep respect for several people that have pushed through the language barrier. Maybe we should decide that this is a thing to keep in mind and let it rest for now? Groeten / Cheers, Wilko _ __ | / o / / _ Arnhem, The Netherlands |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl ___ Powered by FreeBSD ___ http://www.freebsd.org _ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: newbus and isa auto irq
This is not happening for the maddr stuff. I suspect this would do better: if (portsize 0) isa_set_portsize(dev, portsize); if (dvp-id_iobase = 0) isa_set_port(dev, dvp-id_iobase); if (dvp-id_irq != 0) isa_set_irq(dev, ffs(dvp-id_irq) - 1); if (dvp-id_drq != -1) isa_set_drq(dev, dvp-id_drq); if (dvp-id_maddr != 0) isa_set_maddr(dev, (int) dvp-id_maddr - KERNBASE); if (dvp-id_msize != 0) isa_set_msize(dev, dvp-id_msize); I'm not sure about the nothing value for id_drq though, it might need to be 0 - but that's a valid dma channel. IMHO, isa_release_resources() clearing of the default values for the probe hints is a timebomb... I thought about adding a seperate store for the hint values rather than using the id_foo[0] entries, and leaving the tracked resource entries for alloc/free without risking the hints. Cheers, -Peter Off the topic, I think we should replace (dvp-id_maddr - KERNBASE) with kvtop(dvp-id_maddr), too much assumption about vm layout... -lq To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
--- Blind-Carbon-Copy X-Mailer: exmh version 2.0.2 2/24/98 To: Peter Wemm pe...@netplex.com.au, d...@freebsd.org Cc: s...@freebsd.org Subject: Re: HEADS UP Important instructions for -current users! In-reply-to: Your message of Sat, 17 Apr 1999 05:30:41 +0800. 19990416213043.95c7b1...@spinner.netplex.com.au Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Mon, 19 Apr 1999 19:15:18 +0100 From: Brian Somers br...@keep.lan.awfulhak.org As of a few minutes ago, a minimal set of changes to bring the so-calle= d 'new-bus' functionality to the i386 kernel in -current. [.] WOW ! All of a sudden ``halt -p'' works properly on my PCG-747 VIAO = notebook ! Also, S=F8ren's ATA DMA code has started to work... awesome ! Well done Doug associates - and S=F8ren for the ATA stuff. Cheers, -Peter - -- = Brian br...@awfulhak.orgbr...@freebsd.org http://www.Awfulhak.org br...@openbsd.org Don't _EVER_ lose your sense of humour ! br...@uk.freebsd.org --- End of Blind-Carbon-Copy To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: newbus and modem(s)
As Rick Whitesel wrote ... Hi: Just wanted to say that I think the lack of a free-for-all CVS is exactly what is required to consistently move FreeBSD forward. If someone Free-for-all as in 'everybody can do commits' ? This is a joke I hope. There already exists such a thing. It is called Linux (and even there the kernel is controlled). feels they would like to take a different approach, then I say by all means do so. If you can convince people to join your development effort then great!, if not, then great!. Rick Whitesel Scientist NBase-Xyplex rwhite...@nbase-xyplex.com Groeten / Cheers, Wilko _ __ | / o / / _ Arnhem, The Netherlands |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl ___ Powered by FreeBSD ___ http://www.freebsd.org _ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: error building kernel
In message 19990419143825.13fe01...@spinner.netplex.com.au Peter Wemm writes: : I'll bet you've got two 'psm0' lines in the config file.. I got the same error when I had two psm devices in my kernel. Warner To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
PCI VGA card becomes ISA
I noticed that after the latest round of new-bus changes, my PCI VGA card is now recognized as a generic ISA card by the kernel. I don't see any ill effects from this, but the new-bus developers may want to know, in case it breaks something else. The VGA card is a S3 Trio64V+. Here's the dmesg output I get. I don't have an old dmesg output before the changes, but the card was recognized by its name and it was using IRQ 9. Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #5: Mon Apr 19 21:41:42 CEST 1999 b...@gold.amis.net:/usr/home/blaz/FreeBSD/src/sys/compile/GOLD Timecounter i8254 frequency 1193182 Hz CPU: Pentium/P55C (232.88-MHz 586-class CPU) Origin = GenuineIntel Id = 0x543 Stepping=3 Features=0x8001bfFPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX real memory = 67108864 (65536K bytes) config pnp 1 0 os enable config pnp 1 0 port0 0x220 port1 0x530 port2 0x388 port3 0x370 config pnp 1 0 irq0 5 drq0 1 drq1 0 config pnp 2 0 os enable config pnp 2 0 port0 0x280 irq0 10 avail memory = 62435328 (60972K bytes) Preloaded elf kernel kernel at 0xc02b6000. Preloaded userconfig_script /boot/kernel.conf at 0xc02b609c. Probing for PnP devices: CSN 1 Vendor ID: YMH0030 [0x3000a865] Serial 0x80860001 Comp ID: PNPb02f [0x2fb0d041] mss_attach Yamaha SA31 at 0x530 irq 5 dma 1:0 flags 0x10 setting up yamaha registers set yamaha master volume to max pcm1 (CS423x/Yamaha/AD1816 Yamaha SA3 sn 0x80860001) at 0x530-0x537 irq 5 drq 1 flags 0x10 on isa CSN 2 Vendor ID: CPX1501 [0x0115180e] Serial 0x48ed418e Comp ID: PNP80d6 [0xd680d041] ed1: address 00:80:48:ed:41:8e, type NE2000 (16 bit) ed1 (edpnp NE2000 sn 0x48ed418e) at 0x280-0x29f irq 10 on isa npx0: math processor on motherboard npx0: INT 16 interface apm0: APM BIOS on motherboard apm: found APM BIOS version 1.2 pcib0: PCI host bus adapter on motherboard pci0: PCI bus on pcib0 chip0: Intel 82439TX System Controller (MTXC) at device 0.0 on pci0 isab0: Intel 82371AB PCI to ISA bridge at device 7.0 on pci0 chip1: Intel 82371AB Power management controller at device 7.3 on pci0 ahc0: Adaptec 2940 Ultra SCSI adapter at device 14.0 on pci0 ahc0: interrupting at irq 14 ahc0: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs isa0: ISA bus on motherboard fdc0: interrupting at irq 6 fdc0: NEC 72065B or clone at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: 1440-KB 3.5 drive at fdc0 drive 0 atkbdc0: keyboard controller (i8042) at port 0x60 on isa0 atkbd0: AT Keyboard on atkbdc0 atkbd0: interrupting at irq 1 vga0: Generic ISA VGA on isa0 sc0: System console on isa0 sc0: VGA color 16 virtual consoles, flags=0x0 sio0 at port 0x3f8-0x3ff irq 4 on isa0 sio0: type 16550A sio0: interrupting at irq 4 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio1: interrupting at irq 3 isic0 at port 0xd80 irq 15 flags 0x3 on isa0 isic0: Teles S0/16.3 isic0: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2) (Addr=0x960) isic0: HSCX 82525 or 21525 Version 2.1 (AddrA=0x160, AddrB=0x560) isic0: interrupting at irq 15 ppc0 at port 0x378 irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold lpt0: generic printer on ppbus 0 lpt0: Interrupt-driven port ppc0: interrupting at irq 7 Intel Pentium detected, installing workaround for F00F bug i4b: ISDN call control device attached i4bisppp: 4 ISDN SyncPPP device(s) attached i4bctl: ISDN system control port attached i4bipr: 4 IP over raw HDLC ISDN device(s) attached i4btel: 2 ISDN telephony interface device(s) attached i4brbch: 4 raw B channel access device(s) attached i4btrc: 4 ISDN trace device(s) attached Waiting 2 seconds for SCSI devices to settle changing root device to da0s1a da1 at ahc0 bus 0 target 1 lun 0 da1: NEC D3847 0307 Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15) da1: 1547MB (3170160 512 byte sectors: 255H 63S/T 197C) cd0 at ahc0 bus 0 target 3 lun 0 cd0: TEAC CD-ROM CD-532S 3.0A Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present da0 at ahc0 bus 0 target 0 lun 0 da0: IBM DORS-32160 WA6A Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates Blaz Zupan, b...@medinet.si, http://home.amis.net/blaz Medinet d.o.o., Linhartova 21, 2000 Maribor, Slovenia To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: pcm sound driver crashes at boot time.
Russell Cattelan wrote:
I haven't been able to track down exactly where this
is occuring, but disabling pcm allows eliminates the crash.
The build is current as of Sun 18th.
The one strange thing about this box, it has
two sounds cards. A build in Yamaha OPL-3 (really really crappy)
and Ensoniq AudioPCI 1371 (very hacked driver, So the problem may be my
fault).
But I guessing it has more to do with the newbus stuff.
Ok I finally tracked down what was going wrong, I'm not saying I found the
problem
of how to fix it correctly.
The cause:
pcmprobe gets called after es_pci_attach (which has setup the snddev_info
structure),
the first thing pcmprobe does is bzero that structure. Which of course cause a
page fault
the next time that structure is access. (by es_intr in this case)
The really QD fix was to just return from pcmprobe.
int
pcmprobe(struct isa_device * dev)
{
DEB(printf(pcmprobe dev:0x%x name:%s\n,dev,
(pcm_info[dev-id_unit]).name));
/* The AudioPCI probe stuff was done already */
if(!(strncmp ((pcm_info[dev-id_unit]).name,
ES1371,strlen(ES1371{
return 1;
}
bzero(pcm_info[dev-id_unit], sizeof(pcm_info[dev-id_unit]) );
return generic_snd_probe(dev, pcm_devslist, pcm) ? 1 : 0 ;
}
--
Russell Cattelan
catte...@thebarn.com
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message
modules/joy breaks make world
FYI. The recent commit to move sys/sys/lkm.h to the attic breaks make world is sys/module/joy. 1.19 Mon Apr 19 14:19:52 1999 UTC by peter CVS Tags: HEAD Diffs to 1.18 FILE REMOVED Zap LKM option and support. Farewell old friend. -- Steve To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: newbus and modem(s)
Hi: Sorry for my lack of clarity. What I meant was that we DO need control on the cvsup updates. I am perfectly happy with the way the FreeBSD team runs the show. Rick - Original Message - From: Wilko Bulte wi...@yedi.iaf.nl To: Rick Whitesel rwhite...@nbase-xyplex.com Cc: garba...@hooked.net; wghi...@bellsouth.net; gr...@unixhelp.org; d...@newsguy.com; j...@zippy.cdrom.com; curr...@freebsd.org; wghi...@wghicks.bellsouth.net Sent: Monday, April 19, 1999 2:12 PM Subject: Re: newbus and modem(s) As Rick Whitesel wrote ... Hi: Just wanted to say that I think the lack of a free-for-all CVS is exactly what is required to consistently move FreeBSD forward. If someone Free-for-all as in 'everybody can do commits' ? This is a joke I hope. There already exists such a thing. It is called Linux (and even there the kernel is controlled). feels they would like to take a different approach, then I say by all means do so. If you can convince people to join your development effort then great!, if not, then great!. Rick Whitesel Scientist NBase-Xyplex rwhite...@nbase-xyplex.com Groeten / Cheers, Wilko _ __ | / o / / _ Arnhem, The Netherlands |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl ___ Powered by FreeBSD ___ http://www.freebsd.org _ To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/i386/conf LINT GENERIC
Redirected to -current... I seem to recollect that you were having problems in handling interrupts so were are you at with this problem.. Unplug a few devices and you will have the opportunity to review the devices probed in your machine (reboot). I've only removed the list of devices from GENERIC LINT, not from the conf/files and options. Hiding it basically. Nick On Mon, 19 Apr 1999, Amancio Hasty wrote: Curious why is USB not ready for public consumption? Got a USB only system : keyboard + mouse working over here. -- Amancio Hasty ha...@star-gate.com -- e-Mail: hi...@skylink.it -- Amancio Hasty ha...@star-gate.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/i386/conf LINT GENERIC
Currently we have the following: - working drivers for keyboards, mice, hubs - usable driver for USB Zip drive (Iomega, SCSI) (any coders/testers (the true combination) welcome) I am currently finishing the initial workings of the Zip driver and have been able to MSDOS format a disk and been able to read a hfs (iMac) floppy as well. But the driver panics the system when drive unplugged. Planned is: - rewrite of the uhub driver to completely follow newbus (up to now a mixed approach which fails at detach) - start working on 3COM modem support - start working on Ye-Data drive support - start working on Digi 2/4/8 serial port device support - start working on 3COM ISDN adapter support - start working on audio support and while doing this: - solidify the UHCI controller support - solidify the OHCI controller support - improve USBDI The ISDN TA, the Ye-Data drive and Digi serial port device have kindly been provided to me (have not yet arrived though) by the respective hardware vendors. Cherry has provided me with a keyboard (with internal bus powered hub). Anyone care to join? Pick up something fairly straightforward like the audio (Audiocontrol driver). Follow the specs and mail me your comments on the USBDI interface we use. A template driver is the ums mouse driver. Kind regards, Nick Hibma FreeBSD USB project n_hi...@freebsd.org http://www.etla.net/~n_hibma/usb/usb.pl http://www.usb.org/ P.S.: USBDI as in, our version of it. The people from the consortium kicked us out. On Mon, 19 Apr 1999, Amancio Hasty wrote: Redirected to -current... I seem to recollect that you were having problems in handling interrupts so were are you at with this problem.. Unplug a few devices and you will have the opportunity to review the devices probed in your machine (reboot). I've only removed the list of devices from GENERIC LINT, not from the conf/files and options. Hiding it basically. Nick On Mon, 19 Apr 1999, Amancio Hasty wrote: Curious why is USB not ready for public consumption? Got a USB only system : keyboard + mouse working over here. -- Amancio Hasty ha...@star-gate.com -- e-Mail: hi...@skylink.it -- Amancio Hasty ha...@star-gate.com -- e-Mail: hi...@skylink.it To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
USB Development
Insert your e-mail message in your web page under a section titled such as Project Status. What specifically is needed in the driver to unplug and plug a device? Currently we have the following: - working drivers for keyboards, mice, hubs - usable driver for USB Zip drive (Iomega, SCSI) (any coders/testers (the true combination) welcome) I am currently finishing the initial workings of the Zip driver and have been able to MSDOS format a disk and been able to read a hfs (iMac) floppy as well. But the driver panics the system when drive unplugged. Planned is: - rewrite of the uhub driver to completely follow newbus (up to now a mixed approach which fails at detach) - start working on 3COM modem support - start working on Ye-Data drive support - start working on Digi 2/4/8 serial port device support - start working on 3COM ISDN adapter support - start working on audio support and while doing this: - solidify the UHCI controller support - solidify the OHCI controller support - improve USBDI The ISDN TA, the Ye-Data drive and Digi serial port device have kindly been provided to me (have not yet arrived though) by the respective hardware vendors. Cherry has provided me with a keyboard (with internal bus powered hub). Anyone care to join? Pick up something fairly straightforward like the audio (Audiocontrol driver). Follow the specs and mail me your comments on the USBDI interface we use. A template driver is the ums mouse driver. Kind regards, Nick Hibma FreeBSD USB project n_hi...@freebsd.org http://www.etla.net/~n_hibma/usb/usb.pl http://www.usb.org/ P.S.: USBDI as in, our version of it. The people from the consortium kicked us out. On Mon, 19 Apr 1999, Amancio Hasty wrote: Redirected to -current... I seem to recollect that you were having problems in handling interrupts so were are you at with this problem.. Unplug a few devices and you will have the opportunity to review the devices probed in your machine (reboot). I've only removed the list of devices from GENERIC LINT, not from the conf/files and options. Hiding it basically. Nick On Mon, 19 Apr 1999, Amancio Hasty wrote: Curious why is USB not ready for public consumption? Got a USB only system : keyboard + mouse working over here. -- Amancio Hasty ha...@star-gate.com -- e-Mail: hi...@skylink.it -- Amancio Hasty ha...@star-gate.com -- e-Mail: hi...@skylink.it -- Amancio Hasty ha...@star-gate.com To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
x11amp 0.9beta1.1 for linux
just in case anyone would like to know, I have gotten x11amp 0.9beta1.1 for linux working on my FreeBSD-CURRENT cvsupped as of last night. If anyone would like instructions on how I did this, please email me. Kenneth Culver To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Newbus and PCCARD
Before I do a send-pr, I wanted to see if anyone else was having problems with newbus and pccardd. I've got a a 3COM/Megahertz 3CXM556 modem (sio1) and a Xircom 10/100 ethernet card (xe0). Doing a make world and then building a new kernel (with appropriate changes for newbus) renders the modem useless. Dmesg shows that only the xe driver is initialized. Thus, when pccardd goes to allocate resources to the modem it fails. Am I missing something, or is this something that has to be worked out in the newbus code? Thanks in advance... --Jerry 8) Jerry Alexandratos % - % Nothing inhabits my(8 8) alexa...@louie.udel.edu % - %thoughts, and oblivion (8 8) darks...@strauss.udel.edu % - %drives my desires.(8 To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: x11amp 0.9beta1.1 for linux
I would like that. Is it a port, or is it a linux compat thing? On Mon, Apr 19, 1999 at 05:33:28PM -0400, Kenneth Wayne Culver wrote: just in case anyone would like to know, I have gotten x11amp 0.9beta1.1 for linux working on my FreeBSD-CURRENT cvsupped as of last night. If anyone would like instructions on how I did this, please email me. Kenneth Culver -- Shawn === America Held Hostage === Day 2280 for the poor and the middle class. Day 2299 for the rich and the dead. 642 days remaining in the Raw Deal. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Problem upgrading 3.1R to 4.0-current
Hi, I have an Asus P2B-D with 2 PII/350, 128Mb Ram with FreeBSD 3.1R installed. I just added the SMP lines to the generic kernel and I am having constant reboots. I am trying to upgrade to 4.0-current and I updated my source tree tonight around 17:30 UTC but make world gives me errors, at different places each time it is run. I tried in single user, with the GENERIC kernel or with my SMP GENERIC (Generic with just the lines for SMP). Nothing is running on this machine. I also can't do a config GENERIC: it gives only isa's should be connected to nexus for lime 129 and 134. Please help me upgrade to 4.0-current. Thanks! To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: x11amp 0.9beta1.1 for linux
just in case anyone would like to know, I have gotten x11amp 0.9beta1.1 for linux working on my FreeBSD-CURRENT cvsupped as of last night. If anyone would like instructions on how I did this, please email me. Sure! Are you planning on updating the port? If not, I'll do the grunt work for you. Cheers, Jerry Hicks wghi...@bellsouth.net To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: x11amp 0.9beta1.1 for linux
Just make a port :-) - Original Message - From: Kenneth Wayne Culver culv...@wam.umd.edu To: freebsd-current@FreeBSD.ORG Sent: 19. april 1999 23:33 Subject: x11amp 0.9beta1.1 for linux just in case anyone would like to know, I have gotten x11amp 0.9beta1.1 for linux working on my FreeBSD-CURRENT cvsupped as of last night. If anyone would like instructions on how I did this, please email me. Kenneth Culver To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
alright, x11amp instructions
since I am inexperienced at creating ports, I'll just give instructions on how to get the latest linux x11amp to work. First, it won't work with voxware, only pcm or OSS. other than that, here are the instructions: Well, there isn't that much to updating the port. I guess the linux_lib port needs to be updated to include the linux versions of glib and gtk, and the x11amp port is just a straight rpm2targz of the rpms of x11amp's website. All I did was grabbed the latest linux_lib port, the x11amp 0.9 beta1.1.rpm file, and the latest gtk and glib files. I moved all the rpms to the /usr/compat/linux directory, and from there I just untarred and ungzipped them (after rpm2targz). That's all it took. I made a symlink from /usr/compat/linux/usr/X11R6/bin/x11amp to /usr/local/bin so I wouldn't have to change my path. It uses (obviously) the linux emulation because I took binary rpms for everything. Kenneth Culver To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: USB Development
On Mon, 19 Apr 1999, Amancio Hasty wrote: Insert your e-mail message in your web page under a section titled such as Project Status. Good idea. What specifically is needed in the driver to unplug and plug a device? attach is straightforward. detach requires: - disconnect function to handle the fact that the device does no longer respond (intr context) - detach function to delete the device and all its resources (normal context) - driver unload (detach all drivers) Currently the problem lies in the fact that free()/malloc() is called from intr context, resources are completely freed, ongoing transfers are cleaned away, etc. Nick Currently we have the following: - working drivers for keyboards, mice, hubs - usable driver for USB Zip drive (Iomega, SCSI) (any coders/testers (the true combination) welcome) I am currently finishing the initial workings of the Zip driver and have been able to MSDOS format a disk and been able to read a hfs (iMac) floppy as well. But the driver panics the system when drive unplugged. Planned is: - rewrite of the uhub driver to completely follow newbus (up to now a mixed approach which fails at detach) - start working on 3COM modem support - start working on Ye-Data drive support - start working on Digi 2/4/8 serial port device support - start working on 3COM ISDN adapter support - start working on audio support and while doing this: - solidify the UHCI controller support - solidify the OHCI controller support - improve USBDI The ISDN TA, the Ye-Data drive and Digi serial port device have kindly been provided to me (have not yet arrived though) by the respective hardware vendors. Cherry has provided me with a keyboard (with internal bus powered hub). Anyone care to join? Pick up something fairly straightforward like the audio (Audiocontrol driver). Follow the specs and mail me your comments on the USBDI interface we use. A template driver is the ums mouse driver. Kind regards, Nick Hibma FreeBSD USB project n_hi...@freebsd.org http://www.etla.net/~n_hibma/usb/usb.pl http://www.usb.org/ P.S.: USBDI as in, our version of it. The people from the consortium kicked us out. On Mon, 19 Apr 1999, Amancio Hasty wrote: Redirected to -current... I seem to recollect that you were having problems in handling interrupts so were are you at with this problem.. Unplug a few devices and you will have the opportunity to review the devices probed in your machine (reboot). I've only removed the list of devices from GENERIC LINT, not from the conf/files and options. Hiding it basically. Nick On Mon, 19 Apr 1999, Amancio Hasty wrote: Curious why is USB not ready for public consumption? Got a USB only system : keyboard + mouse working over here. -- Amancio Hasty ha...@star-gate.com -- e-Mail: hi...@skylink.it -- Amancio Hasty ha...@star-gate.com -- e-Mail: hi...@skylink.it -- Amancio Hasty ha...@star-gate.com -- e-Mail: hi...@skylink.it To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RE: lnc0: broke for us between 3.1 and 4.0?
lnc0: Memory allocated above 16Mb limit I've just committed a fix for this. It was caused by the change to the way vm_page.c allocates memory Is this fix going into stable? (I'm a little surprised that such a change was considered appropriate for the stable branch in the first place.) -- Richard To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RE: lnc0: broke for us between 3.1 and 4.0?
-Original Message- From: Richard Tobin [mailto:rich...@cogsci.ed.ac.uk] Sent: 19 April 1999 23:59 To: p...@originative.co.uk; freebsd-current@FreeBSD.ORG; freebsd-sta...@freebsd.org Subject: RE: lnc0: broke for us between 3.1 and 4.0? lnc0: Memory allocated above 16Mb limit I've just committed a fix for this. It was caused by the change to the way vm_page.c allocates memory Is this fix going into stable? (I'm a little surprised that such a change was considered appropriate for the stable branch in the first place.) I didn't think the memory allocation change was in stable but I may merge the lnc changes back into -stable anyway since it's a cleaner way of doing things. I've got some other lnc problems to fix first though. Paul. To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
RE: alright, x11amp instructions
On 19-Apr-99 Kenneth Wayne Culver wrote: since I am inexperienced at creating ports, I'll just give instructions on how to get the latest linux x11amp to work. First, it won't work with voxware, only pcm or OSS. other than that, here are the instructions: What does it use that pcm and OSS have that Voxware doesn't? Hmm.. there is a hack to use esound with X11amp - that could alleviate the Voxware problem :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: PCI VGA card becomes ISA
On Mon, 19 Apr 1999, Blaz Zupan wrote: I noticed that after the latest round of new-bus changes, my PCI VGA card is now recognized as a generic ISA card by the kernel. I don't see any ill effects from this, but the new-bus developers may want to know, in case it breaks something else. The VGA card is a S3 Trio64V+. Here's the dmesg output I get. I don't have an old dmesg output before the changes, but the card was recognized by its name and it was using IRQ 9. atkbdc0: keyboard controller (i8042) at port 0x60 on isa0 atkbd0: AT Keyboard on atkbdc0 atkbd0: interrupting at irq 1 vga0: Generic ISA VGA on isa0 Same here with a Generic S3 ViRGE pci card. Apr 15 13:11:59 vanessa /kernel: vga0: S3 ViRGE graphics accelerator\ rev 0x06 int a irq 0 on pci0.3.0 Apr 15 13:11:59 vanessa /kernel: vga0 at 0x3b0-0x3df maddr 0xa\ msize 131072 on isa Apr 15 16:22:59 vanessa /kernel: vga0: S3 ViRGE graphics accelerator\ rev 0x06 int a irq 0 on pci0.3.0 Apr 15 16:22:59 vanessa /kernel: vga0 at 0x3b0-0x3df maddr 0xa\ msize 131072 on isa Apr 16 16:38:14 vanessa /kernel: vga0: S3 ViRGE graphics accelerator\ rev 0x06 int a irq 0 on pci0.3.0 Apr 16 16:38:14 vanessa /kernel: vga0 at 0x3b0-0x3df maddr 0xa\ msize 131072 on isa Apr 17 18:22:32 vanessa /kernel: vga0: Generic ISA VGA on isa0 Apr 17 18:22:32 vanessa /kernel: fb0: vga0, vga, type:VGA (5), flags:0x700ff Apr 19 16:22:34 vanessa /kernel: vga0: Generic ISA VGA on isa0 -- Regards, Kevin G. Eliuk Box 67, Granthams Landing, BC VON 1X0 (604)886-4040 Discover Rock Solid, Discover FreeBSD | http://www.FreeBSD.Org To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
from my understanding, the biggest difference is that New-bus is being designed to eventually delegate 'config' to a very minor role where newconfig (as it's name suggests' maintains 'config' a s a major component.. It has been a long standing goal of FreeBSD to make the system as dynamic as possible. My personal goal is to see it more dynamically configurable than NT with all it's DLLs. julian On Mon, 19 Apr 1999, Tomoaki NISHIYAMA wrote: jkh I don't go to new-bus, this direction is disunion of BSDs. It is jkh bad decision. jkh jkh I'm sorry that you feel this way, but I can only re-state that better jkh communication could have prevented this in the first place and hope jkh that you've learned your own lessons from this exercise. If you jkh haven't, then a good opportunity for learning has simply been wasted. One problem on the decision is that it was not based on a judge that new-bus is technically or philosophically superior to newconfig framework but you stated jkh the difference with new-bus being jkh that we were working just that much more closely with Doug Rabson (and jkh the others helping him) and had already used the new-bus stuff for jkh FreeBSD/alpha. Nakagawa would not be so upset if you could convince him that new-bus were superior. Tomoaki Nishiyama e-mail:tomo...@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: ATTENTION PLEASE: g77 in base system.
On Fri, Apr 09, 1999 at 03:52:58PM +0200, Jeremy Lea wrote: ... Many people don't seem to understand that FreeBSD can be used for workstations as well as servers and Fortran is *essential* on a scientific/engineering workstation. ... Absolutely correct. Some up-and-coming IBM simulation ports require Fortran categorically. It's tough answering questions like FreeB... what? Is that like Linux? Without a STANDARD system Fortran compiler an operating system is unlikely to be taken seriously by ANY large engineering company. We could, however, do without fortune. :-) -- Daniel Ortmann IBM Circuit Technology 2414 30 av NW, #DE315, bldg 040-2 Rochester, MN 55901 3605 Hwy 52 N 507.288.7732 (h) 507.253.6795 (w) ortm...@isl.net ortm...@us.ibm.com -- The answers are so simple and we all know where to look, but it's easier just to avoid the question. -- Kansas To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
From: Julian Elischer jul...@whistle.com Subject: Re: HEADS UP Important instructions for -current users! Date: Mon, 19 Apr 1999 19:59:03 -0700 (PDT) Message-ID: pine.bsf.3.95.990419195617.11256a-100...@current1.whistle.com julian from my understanding, the biggest difference is that New-bus julian is being designed to eventually delegate 'config' to a very minor role julian where newconfig (as it's name suggests' maintains 'config' a s a major julian component. You should not forget that newconfig is a different thing from the old config. It will remove the illness of the old config. julian It has been a long standing goal of FreeBSD to make the system julian as dynamic as possible. My personal goal is to see it more dynamically julian configurable than NT with all it's DLLs. By now, newconfig people decided to continue its development until its dynamic configuration stuff works under FreeBSD, despite the decision to merge newbus into the main CVS repository You can see the implementation of dynamic configuration under newconfig, which means that you have one more chance to integrate newconfig stuff. I hope you have the flexibility to think seriously the integration of newconfig. Currently proposed schedule is on April 21 import sys4c990410 syncing and test around April 28 import PRE_NEWBUS Achievement is now announced in newconfig mailing list (newcon...@jp.freebsd.org, controlled by majord...@jp.freebsd.org). Although most discussion are done in Japanese in newconfig-jp mailing list but any comment, suggestion, or question in English to newcon...@jp.freebsd.org will be appreciated. To make the communication more close, it is possible to post the achievements and plans to hackers or current. Do you think this appropriate? Tomoaki Nishiyama e-mail:tomo...@biol.s.u-tokyo.ac.jp Department of Biological Sciences, Graduate School of Science, The University of Tokyo To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Re: HEADS UP!!!! Important instructions for -current users!
integrate newconfig stuff. I hope you have the flexibility to think seriously the integration of newconfig. As long as it doesn't significantly impact the work already in progress, I think the flexibility is certainly there. To make the communication more close, it is possible to post the achievements and plans to hackers or current. Do you think this appropriate? I think it's more than appropriate, it's *mandatory* if you wish to solve the communication problem. Posting regular updates on your progress on -hackers or -current (depending on applicability) is strongly encouraged. - Jordan To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
Peer review (was: HEADS UP!!!! Important instructions for -current users!)
On Monday, 19 April 1999 at 21:46:30 -0700, Jordan K. Hubbard wrote: integrate newconfig stuff. I hope you have the flexibility to think seriously the integration of newconfig. As long as it doesn't significantly impact the work already in progress, I think the flexibility is certainly there. To make the communication more close, it is possible to post the achievements and plans to hackers or current. Do you think this appropriate? I think it's more than appropriate, it's *mandatory* if you wish to solve the communication problem. Posting regular updates on your progress on -hackers or -current (depending on applicability) is strongly encouraged. But as we have seen, posting on -hackers doesn't guarantee that anybody of any importance will see it. Greg -- See complete headers for address, home page and phone numbers finger g...@lemis.com for PGP public key To Unsubscribe: send mail to majord...@freebsd.org with unsubscribe freebsd-current in the body of the message
