Major number for PCDMX driver?

2000-01-16 Thread Michael Sperber [Mr. Preprocessor]
Hi, I've written a driver for SoundLight's PCDMX DMX512 boards. (DMX512 is a serial protocol used for driving theater and show lighting systems.) I plan to make it available via SoundLight's web site. The potential user base for this is not large enough to warrant inclusion into the kernel (i

Re: Dell PowerEdge 2400 & RCC PCI chipset?

2000-01-16 Thread NOKUBI Hirotaka
In message <[EMAIL PROTECTED]>, Warner Losh writes: >: My NEC PC98 (using x86 CPU, but not PC-AT compatible) uses >: RCC Champion as it's chipset. (Sorry not Champion II/III, it's slightly >: old machine.) I'll attach dmesg from it. >: >: RCC Champion is attached like this. >: > pcib0: on mothe

Anyone working on a DOMEX scsi driver ?

2000-01-16 Thread Thierry Herbelot
Hello, I've just bought a Mustek SCSI scanner, and it is bundled with a seemingly very simple SCSI controller built by a DOMEX company (from Taiwan) Does someone know where there could be some info ? (perhaps a driver under Linux ?) TfH PS : the board identifier is DMX3191D - the chip

Re: Use of newbus in sys/pci/pci.c

2000-01-16 Thread Doug Rabson
On Sat, 15 Jan 2000, Michael Kennett wrote: > Hello All, > > I have a question on the sys/pci/pci.c code, and its use of the > newbus architecture. An example of the code in question is: > > static struct resource * > pci_alloc_resource(device_t dev, device_t child, int type, int *rid, >

Re: Dell PowerEdge 2400 & RCC PCI chipset?

2000-01-16 Thread Warner Losh
In message <[EMAIL PROTECTED]> NOKUBI Hirotaka writes: : >From Jul-1999 to Dec-1999, 4.0-current had a problem in i386/isa/pcibus.c. : It does not have any relations with pccard, don't worry. : : I've sent PR (kern/15278) and it's committed on 1999/12/5. : Problem is solved now. Thanks. I just

Re: Dell PowerEdge 2400 & RCC PCI chipset?

2000-01-16 Thread Jeroen Ruigrok/Asmodai
[ Please strip either smp or hackers on the next replies ] -On [2112 00:00], Kenneth D. Merry ([EMAIL PROTECTED]) wrote: > >Anyone have a URL for RCC? I just spend 30 minutes digging. No URL to be find. All tech forums have URL's for all participants, except for RCC (Reliance Computer Corp

Re: How to write a device-driver?

2000-01-16 Thread Jeroen Ruigrok/Asmodai
-On [2109 04:01], Joachim Jdckel ([EMAIL PROTECTED]) wrote: >Hello. Hi, >This is the first time that I try to do a hardware related programming, >(if I ever will start and finish it...) >I'm currently have no knowledge of that kind of programming, but I'd >like to learn! Welcome to the club

PANIC in 3.4-STABLE

2000-01-16 Thread David E. Cross
I have found a reproduceable panic in recent 3.4-STABLE images (past couple of weeks). I am not sure how to reproduce it thought ;) The panic occurs in the tty code it would appear. It is often preceded by strange TTY behavior (strange characters suddenly appearing in the output, a randomly clo

Re: Major number for PCDMX driver?

2000-01-16 Thread Doug Russell
On 16 Jan 2000, Michael Sperber [Mr. Preprocessor] wrote: > > Hi, > > I've written a driver for SoundLight's PCDMX DMX512 boards. (DMX512 WooHoo! :) I was hoping someone would get a DMX512 controller working before I had to break down and do it myself. :) I've never seen a SoundLight bo

Re: Anyone working on a DOMEX scsi driver ?

2000-01-16 Thread Doug Russell
On Sun, 16 Jan 2000, Thierry Herbelot wrote: > I've just bought a Mustek SCSI scanner, and it is bundled with a > seemingly very simple SCSI controller built by a DOMEX company (from > Taiwan) Throw it away. Throw it as far as you can, then drive over it with you car. :) > Does someone know w

Re: question regarding FreeBSD memory mgmt

2000-01-16 Thread Mohit Aron
Hi, thanks for telling me about this. I don't care if it isn't there in 2.2.6, I managed to figure the code out in 3.x and add the appropriate code to 2.2.6 to do just what I wanted. - Mohit >STABLE (3.x) has a memcontrol(8) program that can do just that. > I don't know off hand wh

ypldap

2000-01-16 Thread Chrisy Luke
Any interest in a hack of ypserv that effectively gateways master.passwd, passwd and (shortly, anyway) group maps to an LDAP DB? If so, I'll make it available. Very configurable. :-) Got it working a few hours ago. Need's tidying up, but otherwise seemingly sound. It's essentially a drop in repla

Re: ypldap

2000-01-16 Thread Matthew Jacob
Yes- this would be a cool thing. On Mon, 17 Jan 2000, Chrisy Luke wrote: > Any interest in a hack of ypserv that effectively gateways > master.passwd, passwd and (shortly, anyway) group maps to > an LDAP DB? If so, I'll make it available. > > Very configurable. :-) Got it working a few hours

Re: looking for victims, err, uh, 'volunteers'

2000-01-16 Thread Matthew Jacob
> > I've got a Compaq Proliant 3000 with three drives in a hot-plug > chassis that I was told by someone else a while back (you?) speak > SAF-TE. Unfortunately, I'm running -STABLE on that box. If this > would happen to work with -STABLE, If all goes well, I'll do a MFC next week or so. >

Re: How to write a device-driver?

2000-01-16 Thread Juergen Lock
In article <[EMAIL PROTECTED]> you write: >-On [2109 04:01], Joachim Jdckel ([EMAIL PROTECTED]) wrote: >>And maybe you could give me a tip, whats the best point to start, a >>linux-device-driver, something like a specification of the different >>chips on the card (it seems, that there is no d

Re: ypldap

2000-01-16 Thread David E. Cross
I for one am very interested in this technology. -- David Cross | email: [EMAIL PROTECTED] Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute,

Re: looking for victims, err, uh, 'volunteers'

2000-01-16 Thread Chris Dillon
On Sun, 16 Jan 2000, Matthew Jacob wrote: > > > > > I've got a Compaq Proliant 3000 with three drives in a hot-plug > > chassis that I was told by someone else a while back (you?) speak > > SAF-TE. Unfortunately, I'm running -STABLE on that box. If this > > would happen to work with -STABLE,

Re: looking for victims, err, uh, 'volunteers'

2000-01-16 Thread Matthew Jacob
> Hmm... I guess I was confusing this with the S.M.A.R.T. stuff that is > supposed to give you a kind of pre-emptive warning that bad things are > going to happen (or have happened, rather... i.e. the drive starts > reallocating a bunch of blocks or senses some other kind of internal > problem).

Preemptiveness of FreeBSD threads

2000-01-16 Thread Alexander Litvin
Hi, everybody! First, I must say that this all concernes quite current CURRENT (Jan 9 or so). I don't know if the same holds for older versions. I'm kind of puzzled. I've a simple sample program (see at the bottom). It creates 10 threads with start function start_my_thread(), and then runs the

Re: Preemptiveness of FreeBSD threads

2000-01-16 Thread Daniel Eischen
Alexander Litvin wrote:> First, I must say that this all concernes quite current > CURRENT (Jan 9 or so). I don't know if the same holds for > older versions. > > I'm kind of puzzled. > > I've a simple sample program (see at the bottom). It creates 10 > threads with start function start_my_thre

Re: Preemptiveness of FreeBSD threads

2000-01-16 Thread Michael Bacarella
> I'm kind of puzzled. > Program, when killed with SIGINT, prints all counters and exits. > Depending on the phase of the moon (it seems) sometimes my > program gives (after ^C): > This result is obtained for approximately the same runtime of the > program. The same picture from 'ps'. I'm star

Re: Preemptiveness of FreeBSD threads

2000-01-16 Thread Jean-Marc Zucconi
I also have this problem it seems: $ cc a.c -pthread $ a.out ^C Thread 0x00: 0 Thread 0x01: 0 Thread 0x02: 0 Thread 0x03: 0 Thread 0x04: 0 Thread 0x05: 0 Thread 0x06: 0 Thread 0x07: 0 Thread 0x08: 0 Thread 0x09: 0 Thread 0x0a: 162033094 Excepted that the phases of the moon do not play - It's alwa

Re: Preemptiveness of FreeBSD threads

2000-01-16 Thread Michael Bacarella
> Program, when killed with SIGINT, prints all counters and exits. > > Now, as I understand, userspace threads in FreeBSD are preemptive. > So, though my 11 threads are all computational and do not do > any syscalls, sleeps, sched_yield, whatever -- newertheless, > the program should not be stuc

Re: Preemptiveness of FreeBSD threads

2000-01-16 Thread Wes Peters
Daniel Eischen wrote: > > Alexander Litvin wrote: > > First, I must say that this all concernes quite current > > CURRENT (Jan 9 or so). I don't know if the same holds for > > older versions. > > > > I'm kind of puzzled. > > > > I've a simple sample program (see at the bottom). It creates 10 > >

Re: Preemptiveness of FreeBSD threads

2000-01-16 Thread Wes Peters
Michael Bacarella wrote: > > > Program, when killed with SIGINT, prints all counters and exits. > > > > Now, as I understand, userspace threads in FreeBSD are preemptive. > > So, though my 11 threads are all computational and do not do > > any syscalls, sleeps, sched_yield, whatever -- newerthele

Hackers in space?

2000-01-16 Thread Wes Peters
irc.core.com died, long live the king. Where did my favorite IRC channel disappear to? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC [EMAIL PROTECTED]

Re: "very dangerously dedicated mode" is

2000-01-16 Thread Jim Shankland
[Re: FreeBSD wedges even booting from a floppy when wd0's slice table contains executable code]: Jamie Bowden <[EMAIL PROTECTED]> writes: > If it were SCSI I'd say plug it in to the nearest adaptec > controller and low level it (I fixed a drive one of my SGI's > ate like this), but it's IDE. Y

Re: Preemptiveness of FreeBSD threads

2000-01-16 Thread Jason Evans
On Sun, Jan 16, 2000 at 10:18:56PM -0700, Wes Peters wrote: > Michael Bacarella wrote: > > > > > Program, when killed with SIGINT, prints all counters and exits. > > > > > > Now, as I understand, userspace threads in FreeBSD are preemptive. > > > So, though my 11 threads are all computational and

Re: Preemptiveness of FreeBSD threads

2000-01-16 Thread Reinier Bezuidenhout
Hi ... I also ran this program on a 4.0-current as of about Jan 13 2000 :) It generates the errornous output like clock work on my machine (after about 30 tries - no exception). I then though that maybe the system gets so buzy that it has difficulty on starting the threads - yes I know this sho

Re: Preemptiveness of FreeBSD threads

2000-01-16 Thread Jason Evans
On Sun, Jan 16, 2000 at 10:50:45PM -0500, Alexander Litvin wrote: > I've a simple sample program (see at the bottom). It creates 10 > threads with start function start_my_thread(), and then runs the > same function in main(). So, we have 11 threads doing the same job. > > Function start_my_thread

Re: Preemptiveness of FreeBSD threads

2000-01-16 Thread Alexander Litvin
In article <[EMAIL PROTECTED]> you wrote: >> Now, as I understand, userspace threads in FreeBSD are preemptive. >> So, though my 11 threads are all computational and do not do >> any syscalls, sleeps, sched_yield, whatever -- newertheless, >> the program should not be stuck in one thread. And it

Re: Preemptiveness of FreeBSD threads

2000-01-16 Thread Reinier Bezuidenhout
> Hi ... > > I also ran this program on a 4.0-current as of about Jan 13 2000 :) > > It generates the errornous output like clock work on my machine (after about > 30 tries - no exception). I then though that maybe the system gets so buzy > that it has difficulty on starting the threads - yes I

Re: Preemptiveness of FreeBSD threads

2000-01-16 Thread Wes Peters
Jason Evans wrote: > > You don't mention how long you run the program for, so I'm assuming that > the runtime must be quite short for you to be seeing the results that > concerned you. All tests that I ran showed non-zero counters for all > threads if the program ran for more than 1.5 seconds.

Re: Preemptiveness of FreeBSD threads

2000-01-16 Thread Reinier Bezuidenhout
> My experiments with your test program do exactly what I would expect. The > longer the program is run, thu longer the program has to preempt threads, > which means that given enough time, all threads will run. If the program > is run for a short time (less than about 1.5 seconds) then some thr

Re: looking for victims, err, uh, 'volunteers'

2000-01-16 Thread Kenneth D. Merry
On Sun, Jan 16, 2000 at 17:56:41 -0800, Matthew Jacob wrote: > > > Hmm... I guess I was confusing this with the S.M.A.R.T. stuff that is > > supposed to give you a kind of pre-emptive warning that bad things are > > going to happen (or have happened, rather... i.e. the drive starts > > reallocati

Re: looking for victims, err, uh, 'volunteers'

2000-01-16 Thread Matthew Jacob
SMART is IDE, I believe.. and unless somebody hits Soren over the head, we're not gonna have even ATAPI to try SMART with. On Sun, 16 Jan 2000, Kenneth D. Merry wrote: > On Sun, Jan 16, 2000 at 17:56:41 -0800, Matthew Jacob wrote: > > > > > Hmm... I guess I was confusing this with the S.M.A.R

Re: libelf and Elf Interface Routines

2000-01-16 Thread Ville-Pertti Keinonen
[EMAIL PROTECTED] (Ronald F. Guilmette) writes: > The original libelf code was/is owned by, and developed by AT&T's Unix > Systems Group (USG) which AT&T sold to (I think) Novell and which Novell > then sold to SCO. > Bottom line is that the _real_ libelf is proprietary code. There is a free (

Re: Preemptiveness of FreeBSD threads

2000-01-16 Thread Jason Evans
On Sun, Jan 16, 2000 at 11:45:12PM -0700, Wes Peters wrote: > Jason Evans wrote: > > > > You don't mention how long you run the program for, so I'm assuming that > > the runtime must be quite short for you to be seeing the results that > > concerned you. All tests that I ran showed non-zero coun