In message <[EMAIL PROTECTED]> Christopher Masto writes:
: Well, here's all I've got. It's basically just a sloppy version of
: what you suggested.
I've cleaned this up, worked it around, and managed to insert and
eject my ep card 5 times in a row on my desktop kludge environment.
It even appear
On Wed, 1 Dec 1999, Dmitrij Tejblum wrote:
> Bruce Evans wrote:
> > I would have
> > expected the most generally efficient way to align doubles and the new PIII
> > obkects to be aligning the stack only in functions that have such objects
j
> > on the stack. This requires at most one extr
On a freebsd-current box there is a second scsi-cdrom (a cd-writer
working fine with cdrecord). I remade the devices with MAKEDEV,
everything is new, but there is nothing new like cd1c ... Looking at the
source the minor number of cd0c has to be increased by 8.
--
Fritz Heinrichmeyer mailto:[EMAI
> > that it requires libc_r.so.3; unfortunately, compat3x does not contain
> > this lib. Any chance of having it added to compat3x?
>
> Yes. The PR is assigned to me, but David already has it on his TODO
> list. Compat3x is updated late to make sure the latest libraries are in.
Until 3.4-REL (w
In message <[EMAIL PROTECTED]> Christopher Masto writes:
: On Tue, Nov 30, 1999 at 04:52:33PM -0700, Warner Losh wrote:
: > It would help me if you could send me your patches...
:
: Well, here's all I've got. It's basically just a sloppy version of
: what you suggested.
OK. This should help.
On Tue, Nov 30, 1999 at 04:52:33PM -0700, Warner Losh wrote:
> It would help me if you could send me your patches...
Well, here's all I've got. It's basically just a sloppy version of
what you suggested.
Index: pccard.c
===
RCS fil
:> I guess only if you do have a PIII and are using the new instructions.
:> In most cases this has no effect whatsoever. Not counting the
:> significant code size increase.
:
:It's also useful for properly aligning doubles on the stack. I would have
:expected the most generally efficient way to
In article <[EMAIL PROTECTED]>,
Garrett Wollman <[EMAIL PROTECTED]> wrote:
> < said:
>
> > The route disappears from the routing table, but it is
> > not freed. (The Leak.)
>
> Actually, no.
>
> > Now cause some packets to travel on the connection. A new cloned
> > route is created and added
If you have an SB card not probed since the import of the bridge
dirvers, could you please apply the following patch, add the logical
ID of your card into sbc_ids[] and see how it works?
(I have asked peter to review the PnP part of the patch)
Index: sbc.c
=
That's not what I said.
> I just cvsupped about 2 hours ago...
>
> On Tue, 30 Nov 1999, Mike Smith wrote:
>
> > > I tried to rebuild the linux kernel module, but it doesn't work:
> >
> > This is -current. You need to stay up to date.
> >
> > --
> > \\ Give a man a fish, and you feed him for
I just cvsupped about 2 hours ago...
=
| Kenneth Culver | FreeBSD: The best OS around.|
| Unix Systems Administrator | ICQ #: 24767726 |
| and student at The | AIM: AgRSkaterq
> I tried to rebuild the linux kernel module, but it doesn't work:
This is -current. You need to stay up to date.
--
\\ Give a man a fish, and you feed him for a day. \\ Mike Smith
\\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED]
\\ and he'll hate you for a lifetime.
In message <[EMAIL PROTECTED]> Christopher Masto writes:
: Ho hum. sio_pccard_detach also needs to be fixed to return 0, but I
: don't think that explains the freeze. Unfortunately, while I can
: sometimes squeeze in a few minutes to try quick fixes, my current
: job doesn't leave me with time t
I tried to rebuild the linux kernel module, but it doesn't work:
Warning: Object directory not changed from original
/usr/src/sys/modules/linux
cc -c -O -pipe -DKERNEL -Wall -Wredundant-decls -Wnested-externs
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline
-Wcast-qual -fforma
In message <[EMAIL PROTECTED]> Mike Smith writes:
: You should definitely check the delete result, yes.
:
: Also, are you calling bus_generic_detach() after deleting the child?
: I got the impression from Doug that this is required...
In the child? device_delete_child() already calls
device_det
> Hmmm... That's something... How do you know that the delete_child is
> failing? An if printing that it failed or conjecture based on the
> insertion results?
You should definitely check the delete result, yes.
Also, are you calling bus_generic_detach() after deleting the child?
I got the im
I'm on my way out for dinner, just thought I'd mention the latest
experiment results.
On Tue, Nov 30, 1999 at 04:19:18PM -0700, Warner Losh wrote:
> : And further data on the CDPD card.. removing it while PPP is still
> : running just paniced in sioioctl. However, the delete_child didn't
> : fai
In message <[EMAIL PROTECTED]> Christopher Masto writes:
: I added a check of the return value. It seemed to be returning 12
: (ENOMEM), but I'm not sure if that's real or garbage, since I'm having
: trouble finding a code path that would return that.
You might want to make ed_pccard_detach retu
On Tue, Nov 30, 1999 at 04:04:40PM -0700, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Christopher Masto writes:
> : Hey, we're getting somewhere. It works, in that it stops the panic.
> : I get the "ed0: unloaded" message, and the machine doesn't panic, but
> : there are still some proble
In message <[EMAIL PROTECTED]> Christopher Masto writes:
: It's not quite working. I think I got away ok with the ethernet card
: because it wasn't being accessed, but my CDPD card with a running PPP
: session pretty reliably still freezes up. Hrm. No, it's not freezing
: up, it's a panic, but
In message <[EMAIL PROTECTED]> Frank Mayhar writes:
: I'll bet Warner meant
: device_delete_child(pccarddev, kid[i]);
: up there, and not
: device_delete_child(pccarddev, kid[0]);
:
: Did you try that?
Yes. He did. Likely won't make a difference here because we don'
On Tue, Nov 30, 1999 at 02:54:28PM -0800, Frank Mayhar wrote:
> > On Tue, Nov 30, 1999 at 02:59:10PM -0700, Warner Losh wrote:
> > > pccarddev = devclass_get_device(pccard_devclass, slt->slot);
> > > device_get_children(pccarddev, &kids, &nkids)
> > > for (i = 0; i < nkids; i++)
> > >
In message <[EMAIL PROTECTED]> Christopher Masto writes:
: Hey, we're getting somewhere. It works, in that it stops the panic.
: I get the "ed0: unloaded" message, and the machine doesn't panic, but
: there are still some problems. It seems that device_delete_child
: is failing (I forgot to prin
Bruce Evans wrote:
> I would have
> expected the most generally efficient way to align doubles and the new PIII
> obkects to be aligning the stack only in functions that have such objects
> on the stack. This requires at most one extra instruction:
>
> andl $~0xf,$esp 16-byte alig
Christopher Masto wrote:
> On Tue, Nov 30, 1999 at 02:59:10PM -0700, Warner Losh wrote:
> > In message <[EMAIL PROTECTED]> Christopher Masto writes:
> > : I found that the only message printed was "ready to power off".
> >
> > bingo. looks like we're not deleting the child. Try replacing that
>
On Tue, Nov 30, 1999 at 02:59:10PM -0700, Warner Losh wrote:
> In message <[EMAIL PROTECTED]> Christopher Masto writes:
> : I found that the only message printed was "ready to power off".
>
> bingo. looks like we're not deleting the child. Try replacing that
> for loop with something like:
>
>
On Nov 30, Eric Ogren wrote:
>
> After playing around with the configuration program for a little bit, if
> I set the card back to ISA mode (fixed address/irq), the patched driver
> now detects the card.
> As soon as I set the card to PnP, the driver doesn't see it. Based on the
> pnpinfo outpu
In message <[EMAIL PROTECTED]> Christopher Masto writes:
: I found that the only message printed was "ready to power off".
bingo. looks like we're not deleting the child. Try replacing that
for loop with something like:
pccarddev = devclass_get_device(pccard_devclass, slt->slot);
On Tue, 30 Nov 1999, Matthew N. Dodd wrote:
> On Mon, 29 Nov 1999, Eric Ogren wrote:
>
> > Already there (I can attach my entire config file / dmesg output
> > to anyone who wants to see it, but I didn't want to dump the whole
> > thing to the list).
>
> How about the output of 'pnpinfo'?
After playing around with the configuration program for a little bit, if
I set the card back to ISA mode (fixed address/irq), the patched driver
now detects the card.
As soon as I set the card to PnP, the driver doesn't see it. Based on the
pnpinfo output, I assume this must be something to do
In message <[EMAIL PROTECTED]> Christopher Masto writes:
: I noticed that the "new" code does the power off before the
: reset.. dunno if this is significant.
Shouldn't be... I gotta get a bouncer system that I can plug a bridge
into to see if I can get this problem to happen for me (which i thi
On Tue, Nov 30, 1999 at 08:09:41PM +0100, Nick Hibma wrote:
>
> With freeze I meant, freeze. Rock solid. Nothing to be done. Stepping
> through the code the laptop freezes in the second putb in pcic_disable.
> As in stepping the assembler to that outb does never return the prompt.
I certainly ha
On Tue, 30 Nov 1999, Davec wrote:
> On Tue, 30 Nov 1999, Dan Langille wrote:
>
> > FWIW, I just fetched the tarball from the website and started a compile.
> > It gets further than the previous attempt. My suggestion to Davec is
> > that he try the instructions at:
> >
> > http://www.freebs
With freeze I meant, freeze. Rock solid. Nothing to be done. Stepping
through the code the laptop freezes in the second putb in pcic_disable.
As in stepping the assembler to that outb does never return the prompt.
Nick
> >From some very brief testing here, the problem is that the card's
> int
I just went to the Oct. 7th snap of -CURRENT (right before IP Filter was
removed from FreeBSD 4.0-CURRENT's source tree). Would this warning have
anything to do with ipl not working in the latest snap?
WARNING: driver ipl should register devices with make_dev() (dev_t = "#ipl/1")
As I recall, th
I'm having problems running vat with newpcm: after opening the
device the sound begins for a fraction of a second, then stops.
Maybe this has to do with the fact that vat uses /dev/audio and
not /dev/dsp; I've tried to open /dev/dsp instead and change the
device format but the result is the same.
In message <[EMAIL PROTECTED]> Frank Mayhar writes:
: Personally, I think this is a needed enhancement for MAKEDEV. IMHO, it
: violates the POLA that a "MAKEDEV all" doesn't make _all_ the necessary
: devices to run one's system.
That's one of the reasons that there is a strong desire to have
de
On Tue, 30 Nov 1999, Marcel Moolenaar wrote:
> Matthew Dillon wrote:
>
> > All I can say to that is "bleh". The real question is whether performance
> > is actually improved significantly or not. If not, I'd sent a nasty email
> > to the gcc folks :-)
>
> I guess only if you do ha
In message <[EMAIL PROTECTED]> Mitsuru IWASAKI writes:
: Hi, here is the Nov. progress report from ACPI project in Japan.
Cool. This is indeed good news. Keep up the good reports.
iwasaki-san to acpi-jp wa domo arigato gozaimasu.
Warner
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "u
Matthew Dillon wrote:
> All I can say to that is "bleh". The real question is whether performance
> is actually improved significantly or not. If not, I'd sent a nasty email
> to the gcc folks :-)
I guess only if you do have a PIII and are using the new instructions.
In most cases
:> I can't think of a single case where the stack isn't inherently
:> 4-byte aligned already, whether you use the option or not.
:
:It's more a case of overriding the new behaviour of gcc to align the
:stack on 16-byte boundaries by default (for performance reasons for the
:PIII SIMD instr
"Chris D. Faulhaber" wrote:
>
> I am in the midst of updating one of my ports, net/elsa, and have found
> that it requires libc_r.so.3; unfortunately, compat3x does not contain
> this lib. Any chance of having it added to compat3x?
Yes. The PR is assigned to me, but David already has it on his
On Tue, Nov 30, 1999 at 12:27:53PM -0500, Thomas Stromberg wrote:
> I thought all I needed to do was "./MAKEDEV all" in /dev after a
> mergemaster (I also tried MAKEDEV drive) However, I guess this is not
> the case. Evidentally if I makedev a drive or all, it does not MAKEDEV
> the slices. I coul
In message <[EMAIL PROTECTED]> Mike Smith writes:
: If I'm correct, this is just an ordering issue; the driver has to be shut
: down _before_ the slot, not afterwards.
Right. The code that is doing the shutdown is trying to shutdown the
driver, but that doesn't seem to be happening. The other
Hi,
MDF_ACTIVE in /sys/pccard/cardinfo has another meaning (and value) than
/sys/sys/memrange.h:
cardinfo.h:#define MDF_ACTIVE 0x40 /* Context active (read-only) */
memrange.h:#define MDF_ACTIVE (1<<27) /* currently active */
This breaks kdump (YMMV. In this case it's a -current source tree on a
Thomas Stromberg wrote:
> I thought all I needed to do was "./MAKEDEV all" in /dev after a
> mergemaster (I also tried MAKEDEV drive) However, I guess this is not
> the case. Evidentally if I makedev a drive or all, it does not MAKEDEV
> the slices. I could of sworn it was supposed to.. alas! Lear
In message <[EMAIL PROTECTED]>, Frank Mayhar writes:
>Thomas Stromberg wrote:
>> I thought all I needed to do was "./MAKEDEV all" in /dev after a
>> mergemaster (I also tried MAKEDEV drive) However, I guess this is not
>> the case. Evidentally if I makedev a drive or all, it does not MAKEDEV
>> th
On Tue, 30 Nov 1999, Thomas Stromberg wrote:
[ache wrote]:
> "
> > I see no needs of this change. I have -current dumpon/savecore work with
> > old entrly like /dev/wd0...
> > savecore understand both character and old block devices now.
You must not have a very current -current :-). /dev/wd0 i
I am in the midst of updating one of my ports, net/elsa, and have found
that it requires libc_r.so.3; unfortunately, compat3x does not contain
this lib. Any chance of having it added to compat3x?
-
Chris D. Faulhaber | You can ISO9001 certify the process of
System/Network Adm
Matthew Dillon wrote:
>
> :> > Anyhow, I'll repeat it here - stack alignment does *not* break
> :> > link-compatibility. It does not change calling conventions, it just
> :> > adds padding after the args to ensure that local variables can be
> :> > predictably aligned.
> :
> :> So, how does alig
"Andrey A. Chernov" wrote:
>
> On Tue, Nov 30, 1999 at 10:49:57AM -0500, Thomas Stromberg wrote:
> > [root@karma] dumpon> dumpon /dev/wd0s1b
> > dumpon: /dev/wd0s1b: must specify a block device
> > [root@karma] dumpon> dumpon /dev/rwd0s1b
> > [root@karma] dumpon>
> >
> > Bug or Feature?
>
> This
>From some very brief testing here, the problem is that the card's
interrupt handler hasn't yet been disconected. When you power the card
down, you get an edge on the interrupt pin, and then the driver interrupt
handler spins madly because the card hardware is gone and thus doesn't
behave.
:> > Anyhow, I'll repeat it here - stack alignment does *not* break
:> > link-compatibility. It does not change calling conventions, it just
:> > adds padding after the args to ensure that local variables can be
:> > predictably aligned.
:
:> So, how does aligning stackframes affect the inherentl
On Tue, 30 Nov 1999, Dan Langille wrote:
> FWIW, I just fetched the tarball from the website and started a compile.
> It gets further than the previous attempt. My suggestion to Davec is
> that he try the instructions at:
>
> http://www.freebsddiary.org/freebsd/ipfilter333.htm
>
> I know th
:> that doesn't work, and there's any chance of getting a kernel dump,
:> try getting a kernel dump. Make sure you use a debug (compiled -g)
:> kernel.
:>
:
:While I can't say I truly see the correlation, you definitely know more
:about how it works then me. I've cvsupp'd and upped
On Tue, 30 Nov 1999, Thomas Stromberg wrote:
> "
> > I see no needs of this change. I have -current dumpon/savecore work with
> > old entrly like /dev/wd0...
> > savecore understand both character and old block devices now.
> >
>
> While I see your commit in cvsweb to savecore, I still run into
>From: Martin Hopkins <[EMAIL PROTECTED]>
>Date: Tue, 30 Nov 1999 16:31:30 + (GMT)
>Why is the ??) not a trigraph? ie. (???) => (?]
Right you are; my error. :-(
Cheers,
david
--
David Wolfskill [EMAIL PROTECTED] UNIX System Administrator
voice: (650) 577-7158 pager: (888
"Daniel C. Sobral" wrote:
> Marcel Moolenaar wrote:
> >
> > Julian Elischer wrote:
> > >
> > > When did this come in? (I have been seeing it for a while but..
> > > I thought this was to save space on the bootblocks, not the entire
> > > kernel?)
> >
> > Shortly after setting it for the bootbloc
"Daniel C. Sobral" wrote:
>
> Marcel Moolenaar wrote:
> >
> > Julian Elischer wrote:
> > >
> > > When did this come in? (I have been seeing it for a while but..
> > > I thought this was to save space on the bootblocks, not the entire
> > > kernel?)
> >
> > Shortly after setting it for the bootblo
> {"/usr/src/sys/netinet6"}$ grep '??.' in6.c
> * SIOCGLIFADDR: get first address. (???)
>
> I think the way this has been fixed before is to change it to something
> like (?!?) =)
I adopted the fix, thanks.
Yoshinobu Inoue
> --
> Brian Fundakowski Feldman \ FreeBSD: The Pow
> "David" == David Wolfskill <[EMAIL PROTECTED]> writes:
>> From: [EMAIL PROTECTED]
>> Date: Tue, 30 Nov 1999 23:02:21 +0900
>>> ../../netinet6/in6.c: warning: 1 trigraph(s) encountered
>>> haven't seen one of THOSE for a while
>> Could you tell me which line was th
On Tue, Nov 30, 1999 at 10:49:57AM -0500, Thomas Stromberg wrote:
> [root@karma] dumpon> dumpon /dev/wd0s1b
> dumpon: /dev/wd0s1b: must specify a block device
> [root@karma] dumpon> dumpon /dev/rwd0s1b
> [root@karma] dumpon>
>
> Bug or Feature?
This message is confusing and means just opposite
"
> I see no needs of this change. I have -current dumpon/savecore work with
> old entrly like /dev/wd0...
> savecore understand both character and old block devices now.
>
While I see your commit in cvsweb to savecore, I still run into this
(just cvsupp'd off of cvsup6.freebsd.org and rebuilt i
Marcel Moolenaar wrote:
>
> Julian Elischer wrote:
> >
> > When did this come in? (I have been seeing it for a while but..
> > I thought this was to save space on the bootblocks, not the entire
> > kernel?)
>
> Shortly after setting it for the bootblock. It breaks backward
> compatibility and bo
>From: [EMAIL PROTECTED]
>Date: Tue, 30 Nov 1999 23:02:21 +0900
>>../../netinet6/in6.c: warning: 1 trigraph(s) encountered
>>haven't seen one of THOSE for a while
> Could you tell me which line was that? I don't see any...
Indeed. The only line I see (as of the 1.1 version of the f
What's involved in getting a USB mouse working in -CURRENT ?
I have a Micro$oft USB IntelliMouse 1.1A.
I have added everything USB to my kernel (as I'm not using any USB klds)
and have set usbd_enable to YES in /etc/rc.conf.
My kernel and world are up to date as of about 3 hours ago and I have
On Tue, Nov 30, 1999 at 09:37:41AM -0500, Thomas Stromberg wrote:
> You need to make world first or at least rebuild savecore/dumpon, as
> ache made some commits to it this morning.
>
> IE, old dumpdev in /etc/rc.conf: dumpdev="/dev/wd0s1b"
>
> Should be changed to: dumpdev
In message <[EMAIL PROTECTED]> Nick Hibma writes:
: pcic: polling, can't alloc 0
: pcic: polling, can't alloc 0
This isn't your problem, but you might want to assign an interrupt
line to these devices.
Another problem is that I didn't implement the logic in the right way
for the nbk. In many pl
In message <[EMAIL PROTECTED]> Nick Hibma writes:
: The system freezes on powering down a PCCARD slot. From memory the
: location is putb1 called from pcic_disable. The freeze is easy to
: reproduce, just remove the card. When stepping through the code, even
: the debugger prompt does not return a
While this was mentioned in the commit log for dumpon.c by phk, I figure
I'd save you the loss of a kernel core to find out like the one I lost
this morning. In rc.conf (or wherever you load dumpon) make sure you
change it to using a raw device. dumpon no longer accepts block devices,
as they were
The system freezes on powering down a PCCARD slot. From memory the
location is putb1 called from pcic_disable. The freeze is easy to
reproduce, just remove the card. When stepping through the code, even
the debugger prompt does not return after the outb for PCIC_POWER on
line 698 of pcic.c.
This
> :If you notice, both times it crashed on vm_map_insert.
>
> Try bumping up PMAP_SHPGPERPROC. From LINT:
>
> #
> # Set the number of PV entries per process. Increasing this can
> # stop panics related to heavy use of shared memory. However, that can
> # (combined with large amounts of ph
>../../netinet6/in6.c: warning: 1 trigraph(s) encountered
>haven't seen one of THOSE for a while
Could you tell me which line was that? I don't see any...
itojun
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
> > Anyhow, I'll repeat it here - stack alignment does *not* break
> > link-compatibility. It does not change calling conventions, it just
> > adds padding after the args to ensure that local variables can be
> > predictably aligned.
> So, how does aligning stackframes affect the inherently sta
Ville-Pertti Keinonen wrote:
>
> > What about commercial and/or third party KLDs? They fail to work if they
> > don't also set -preferred-stack-boundry=2, right?
>
> Oops, I accidentally replied to this privately.
>
> Anyhow, I'll repeat it here - stack alignment does *not* break
> link-compati
Thus spake Timo Geusch ([EMAIL PROTECTED]):
> I don't if DES did, but I did. Turns out from his dmesg that he has a very
> similar hardware config (which is why I don't include a copy of my dmesg)
> and I am seeing *exactly* the same problems - suddenly my AWE32 is not
> recognized any more.
Sam
> What about commercial and/or third party KLDs? They fail to work if they
> don't also set -preferred-stack-boundry=2, right?
Oops, I accidentally replied to this privately.
Anyhow, I'll repeat it here - stack alignment does *not* break
link-compatibility. It does not change calling conventio
On Tue, 30 Nov 1999, Julian Elischer wrote:
>
>
> ../../netinet6/in6.c: warning: 1 trigraph(s) encountered
>
> haven't seen one of THOSE for a while
>
A warning, or a proper trigraph?
{"/usr/src/sys/netinet6"}$ grep '??.' in6.c
* SIOCGLIFADDR: get first address. (???)
I think th
Julian Elischer wrote:
>
> When did this come in? (I have been seeing it for a while but..
> I thought this was to save space on the bootblocks, not the entire
> kernel?)
Shortly after setting it for the bootblock. It breaks backward
compatibility and bogusly applies to the tools (xxx_genassym)
Ville-Pertti Keinonen wrote:
>
> No, the units are actually powers-of-two and that overrides the
> default of aligning for doubles (which would be useless in the
> kernel).
What about commercial and/or third party KLDs? They fail to work if they
don't also set -preferred-stack-boundry=2, right?
On Wed, 24 Nov 1999, David O'Brien wrote:
> On Wed, Nov 24, 1999 at 09:58:51AM +0200, John Hay wrote:
> > Well the original line is plain wrong if Brian's patch is being used,
> > because there message is a pointer and the size of a pointer is 4.
>
> Yes, yes, yes. Warner and I are *not* that s
Julian Elischer <[EMAIL PROTECTED]> writes:
> When did this come in? (I have been seeing it for a while but..
> I thought this was to save space on the bootblocks, not the entire
> kernel?)
> Do we really want shorts being pushed onto the stack as shorts?
> (This is what this implies)
No, the
When did this come in? (I have been seeing it for a while but..
I thought this was to save space on the bootblocks, not the entire
kernel?)
Do we really want shorts being pushed onto the stack as shorts?
(This is what this implies)
Julian
To Unsubscribe: send mail to [EMAIL PROTECTED]
with
../../netinet6/in6.c: warning: 1 trigraph(s) encountered
haven't seen one of THOSE for a while
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
On Tue, 30 Nov 1999, Mitsuru IWASAKI wrote:
> 5. AML interpreter implementation
> We've just started based on Doug Rabson's acpitest program, but
> parsing AML and managing objects in the name space are almost
> finished. We're going to make configuration utility first with AML
> interpreter i
On Tue, 30 Nov 1999, Timo Geusch wrote:
> On Tue, Nov 30, 1999 at 10:30:28AM +0900, [EMAIL PROTECTED] wrote:
> > On 29 Nov 1999 19:19:24 +0100,
> > Dag-Erling Smorgrav <[EMAIL PROTECTED]> said:
> >
> > Dag-Erling> My SB32 PnP, which had so far worked nicely with newpcm except for the
> > Dag-E
On Mon, 29 Nov 1999, Matthew Dillon wrote:
>
> :
> :>
> :> makeoptions DEBUG="-g"
> :>
> :Easier option..
> :config -g
>
> Actually no. How many people remember to type options after 'config' ?
> Especially if you are juggling more then one kernel config, trying to
> reme
On Tue, 30 Nov 1999 [EMAIL PROTECTED] wrote:
> On Tue, 23 Nov 1999 04:22:39 +0800,
> Peter Wemm <[EMAIL PROTECTED]> said:
>
> >> Mostly, sbc.c is handling PnP ID matching in a totally bogus manner.
>
> Peter> Yes, it's quite bogus and is incompatible with motherboard devices. There
> Peter>
On Tue, 30 Nov 1999, MIHIRA Sanpei Yoshiro wrote:
> >> But kernel probed ESS1888 as pcm0 and ESS1879 as pcm1. I think
> >> this NOTE-PC only has ESS1879 sound chip and I only use pcm1. I
> >> don't want to probe ESS1888. How can I solve below problem?
> >
> >In retrospect, the es1888 probe c
On Tue, Nov 30, 1999 at 10:30:28AM +0900, [EMAIL PROTECTED] wrote:
> On 29 Nov 1999 19:19:24 +0100,
> Dag-Erling Smorgrav <[EMAIL PROTECTED]> said:
>
> Dag-Erling> My SB32 PnP, which had so far worked nicely with newpcm except for the
> Dag-Erling> "fast forward" bug, stopped working after the
>> But kernel probed ESS1888 as pcm0 and ESS1879 as pcm1. I think
>> this NOTE-PC only has ESS1879 sound chip and I only use pcm1. I
>> don't want to probe ESS1888. How can I solve below problem?
>
>In retrospect, the es1888 probe code I added for alphas was a mistake. I
>will disable that co
On Tue, 30 Nov 1999 02:30:41 -0500 (EST),
Donn Miller <[EMAIL PROTECTED]> said:
>> sbc driver does not probe ESS1868 at this moment.
Donn> Question: will the ESS 1868 bridge driver be incorporated into the sbc
Donn> driver, or should we devise a whole new bridge driver for the ess? I.e.,
Don
92 matches
Mail list logo
