vx driver patch

Someone (I can't find who in my records, please let me know if it was you so I can credit you in the commit message) sent out patches to make the vx driver not use the pci compat shims. I just found it in my home directory, applied it, tweaked things very minorly and it builds and boots.

Re: vx driver patch

At Sun, 05 Nov 2000 01:26:42 -0700, Warner Losh [EMAIL PROTECTED] wrote: I think this means lnc is the last one in the tree, but I could be wrong about that. I didn't do an actual grep... # find /usr/src/sys -type f |xargs grep COMPAT_PCI_DRIVER ./dev/hea/eni.c:COMPAT_PCI_DRIVER (eni_pci,

Re: ABI is broken??

-On [20001102 05:30], Garrett Wollman ([EMAIL PROTECTED]) wrote: On Wed, 1 Nov 2000 14:43:55 -0800, "David O'Brien" [EMAIL PROTECTED] said: Any reason to not get [libc ABI changes] in -current now and make the bump? Mostly because they're too small to be worth the pain. I'm waiting for

weird crash with a corrupt lock (?)

With nothing special going on (I think maybe a tar xfvz of the jdk 1.2.2 source), my system crashed inexplicably. I have no idea why a lock would look like this does, no clue whether I should be replacing my hardware or the system is just getting more and more unstable. (kgdb) p *lkp $1 = {

Re: silly dependencies

On Sat, 4 Nov 2000, Julian Elischer wrote: The following dependencies seem to be wrong in the code.. if you do not define inet, (e.g for a process controller with no networking) then uipc_accf.o will not link because it (wrongly) has it's sysctl linked off 'net.inet' instead of 'net'.

Re: COMPAT_43 [was: Re: silly dependencies]

Bruce Evans wrote: c -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -I../../contrib/dev/acpica/Subsystem/Include -D_KERNEL -include

Re: ABI is broken??

On Sun, 5 Nov 2000 13:51:09 +0100, Jeroen Ruigrok van der Werven [EMAIL PROTECTED] said: I also gather it has to do with the Austin project Garrett? Yes and no. The errors have been there since the beginning of time, but I actually noticed them doing review of our implementation wrt the new

Mixer weirdness (SB 64 AWE)

Hi everybody! I am using a recent -CURRENT from: Fri Nov 3 11:24:57 CET 2000 Before this, my SB 64 AWE ISAPnP card worked nicely, also in -CURRENT. Now the volume states are often wedged when the machine boots up, eg only one channel is used of the two, or the volume level is drastically

Re: vx driver patch

There is a minor typo in the URL. The patches are at: http://people.freebsd.org/~imp/if_vx.patch Jim Bloom [EMAIL PROTECTED] Warner Losh wrote: Someone (I can't find who in my records, please let me know if it was you so I can credit you in the commit message) sent out patches to

RE: SB128/ES1370 sound broken since 26th Oct

SB128 sound support has been broken over a week now. I don't who has made changes on 26th Oct but after these changes I can't get any sound out of my machine. Sources cvsupped 25th Oct still worked fine. should be fixed now. (sys/dev/sound/pci/es137x.c rev 1.25) -cg To

RE: Mixer weirdness (SB 64 AWE)

Now the volume states are often wedged when the machine boots up, eg only one channel is used of the two, or the volume level is drastically different on the two channels. The best part is, mixer(8) does not show any of this, and setting it to different values does not seem to influence the

The biggest reason I rearranged the timing output in make world

If you look at make release's output: make release started on Sun Nov 5 23:27:21 GMT 2000* T1 Making hierarchy Installing everything.. elf make world started on Mon Nov 6 00:25:54 GMT 2000 * T2 Rebuilding the temporary build tree stage 1: bootstrap tools

Re: Mixer weirdness (SB 64 AWE)

On Mon, Nov 06, 2000 at 02:52:33AM -, Cameron Grant wrote: Now the volume states are often wedged when the machine boots up, eg only one channel is used of the two, or the volume level is drastically different on the two channels. The best part is, mixer(8) does not show any of this,

Problem with dlopen()/dlsym() after recent crt* changes

After the crt changes the following piece of code, which worked previously, gives a 'host: dlopen() failed: ./module.so: Undefined symbol "__register_frame_info' error message (yeah, I know that it's better to check handle == NULL first, but it's the way some apps work). handle =

Re: Problem with dlopen()/dlsym() after recent crt* changes

After the crt changes the following piece of code, which worked previously, gives a 'host: dlopen() failed: ./module.so: Undefined symbol "__register_frame_info' error message (yeah, I know that it's better to check handle == NULL first, but it's the way some apps work). Huh! So that's why