On Tue, Feb 20, 2001 at 11:31:52AM +1100, CaT wrote:
> On Mon, Feb 19, 2001 at 04:18:40PM -0800, Ion Badulescu wrote:
> > > In my experiments wait_for_cmd timeouts almost always were related to
> > > DumpStats command.
> > > I think, we need to investigate what time constraints are related to
On Tue, Feb 20, 2001 at 03:30:48PM +0900, Augustin Vidovic wrote:
> On Mon, Feb 12, 2001 at 01:00:34AM -0800, Ion Badulescu wrote:
> > > Augustin, could you send the output of `lspci' and `eepro100-diag -ee', please?
> > > (The latter may be taken from ftp://scyld.com/pub/diag/)
> >
> > I'd be
Peter Waltenberg <[EMAIL PROTECTED]> writes:
> Having a PC that booted Linux directly from the (ex-BIOS) ROM , now that
> would be "interesting".
Been there doing that.
http://www.linuxbios.org
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
No sound comes forth from them, not even so much as a whisper.
Thomas Sailer wrote:
> Landsberger Brian J wrote:
>
>> Has anyone been able to get the Apple Pro (the round clear) speakers to
>> work in Linux? I've read the howto's and followed the various steps to
>> no avail. The
On Mon, Feb 12, 2001 at 01:00:34AM -0800, Ion Badulescu wrote:
> > Augustin, could you send the output of `lspci' and `eepro100-diag -ee', please?
> > (The latter may be taken from ftp://scyld.com/pub/diag/)
>
> I'd be curious to see them too.
Ok, here is the output (the status are displayed
Eugene Danilchenko ([EMAIL PROTECTED]) said:
> cd /lib/modules/2.4.1; \
> mkdir -p pcmcia; \
> find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia
> if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.4.1; fi
> depmod: *** Unresolved symbols in
Hello,
i have problem. When i try to install compiled modules (make modules_install) with
kernel 2.4.2, i get this message (tail -7):
cd /lib/modules/2.4.1; \
mkdir -p pcmcia; \
find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia
if [ -r System.map ]; then
Hi
How does SCSI subsystem interact with FC layers in Linux ?
If anyone could give a brief on this or some links or docs on this.
Ciao
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Bill Wendling wrote:
>
> The use of the ternary operator is superfluous, though...and makes the
> code look ugly IMNSHO :).
>
You are correct. Please ignore my thinko.
Tom
--
The Daemons lurk and are dumb. -- Emerson
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
[BERECZ Szabolcs]
> Here is a new syscall. With this you can change the owner of a running
> procces.
> + if (current->euid)
> + return -EPERM;
Use capable().
> + p = find_task_by_pid(pid);
> + p->fsuid = p->euid = p->suid = p->uid = uid;
Race -- you need to
On Mon, 19 Feb 2001, Brian J. Watson wrote:
> Here is an x86 implementation of down_read_trylock() and down_write_trylock()
> for read/write semaphores. As with down_trylock() for exclusive semaphores, they
> don't block if they fail to get the lock. They just return 1, as opposed to 0 in
> the
Bill Wendling wrote:
>
> Also sprach Andre Hedrick:
> } On Mon, 19 Feb 2001, Pozsar Balazs wrote:
> }
> } > from drivers/ide/ide-features.c:
> } >
> } > /*
> } > * All hosts that use the 80c ribbon mus use!
> } > */
> } > byte eighty_ninty_three (ide_drive_t *drive)
> } > {
> } >
Morten,
I'm not subscribed to linux-kernel, but I've been following the list archive
somewhat for the past month (watching 2.4 development so I can figure out
when it is safe to make the jump without too much hassle)
I just bought a Dell Inspiron 4000 laptop a month ago, and have the same
Paul Gortmaker wrote:
>
> Scott Long wrote:
> >
> > I've been poring over the x86 boot code for a while now and I've been
> > considering writing a FAQ on the boot process (mostly for my own use,
>
> [...]
>
> > Does there exist an outline (detailed or not) of the boot process from
> > the
Hi,
I found that acpi driver has some bugs, I compiled the 2.4.2-pre4
kernel with the acpi support option and SMP enabled, it caused hang at the
boot time, but when I disabled the SMP option, it 's OK , so I look
into the acpi driver source code, and I found the acpi idle function
Any idea if suspend/hybernation will be in future kernels?
Shawn.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
Jeff Garzik <[EMAIL PROTECTED]> writes:
> On 20 Feb 2001, Manfred Bartz wrote:
> > I have 3 NICs (2*DEC, 1*3c509) in my gateway (P75, 40M RAM).
> >
> > tulip.o in 2.4.1 insists on selecting 10baseT, no command
> > line option can convince it otherwise. tulip.o in 2.2.16 auto
> > detected media
On Tue, 20 Feb 2001, Alan Cox wrote:
> Date: Tue, 20 Feb 2001 03:12:15 + (GMT)
> From: Alan Cox <[EMAIL PROTECTED]>
> To: Marcelo Tosatti <[EMAIL PROTECTED]>
> Cc: Linus Torvalds <[EMAIL PROTECTED]>,
> lkml <[EMAIL PROTECTED]>
> Subject: Re: [PATCH] exclusive wakeup for lock_buffer
>
>
> --- linux/include/linux/locks.h.orig Mon Feb 19 23:16:50 2001
> +++ linux/include/linux/locks.h Mon Feb 19 23:21:48 2001
> @@ -13,6 +13,7 @@
> * lock buffers.
> */
> extern void __wait_on_buffer(struct buffer_head *);
> +extern void __lock_buffer(struct buffer_head *);
So are we
Here is an x86 implementation of down_read_trylock() and down_write_trylock()
for read/write semaphores. As with down_trylock() for exclusive semaphores, they
don't block if they fail to get the lock. They just return 1, as opposed to 0 in
the success case.
The algorithm should be robust. It
Btw ___wait_on_page() does something similar.
Here goes the patch for both __lock_page() and ___wait_on_page().
--- linux/mm/filemap.c.orig Mon Feb 19 23:51:02 2001
+++ linux/mm/filemap.c Mon Feb 19 23:51:33 2001
@@ -611,11 +611,11 @@
add_wait_queue(>wait, );
do {
-
Hi,
On Tue, 20 Feb 2001, Neil Brown wrote:
> 2/ lookup("..").
A small question:
Why exactly is this needed?
bye, Roman
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
I asked Kurt why it was not submitted to the mainstream kernel. He said that
some people are still experiencing problems with the card/driver and he doesn't
feel it's stable enough to go in. I'm personally using it with no issues, but
I'm only driving a CD-RW - not exactly stressing things.
It
On Mon, 19 Feb 2001, Linus Torvalds wrote:
>
>
> On Mon, 19 Feb 2001, Marcelo Tosatti wrote:
> >
> > The following patch makes lock_buffer() use the exclusive wakeup scheme
> > added in 2.3.
>
> Ugh, This is horrible.
>
> You should NOT have one function that does two completely different
Alan Cox writes:
>> This may seem like a lot, but several of these are already
>> requirements which most filesystems don't meet, and other are there
>> to tidy-up interfaces and make locking more straight forward.
>
>As a 2.5 thing it sounds like a very sensible path. It will also provide
On Mon, 19 Feb 2001, Marcelo Tosatti wrote:
>
> The following patch makes lock_buffer() use the exclusive wakeup scheme
> added in 2.3.
Ugh, This is horrible.
You should NOT have one function that does two completely different things
depending on a flag. That way lies madness and bad coding
Hi,
The following patch makes lock_buffer() use the exclusive wakeup scheme
added in 2.3.
Against 2.4.2pre4.
--- linux/fs/buffer.c.orig Mon Feb 19 23:13:08 2001
+++ linux/fs/buffer.c Mon Feb 19 23:16:26 2001
@@ -142,13 +142,18 @@
* if 'b_wait' is set before calling this, so that
On Tuesday February 20, [EMAIL PROTECTED] wrote:
> > This may seem like a lot, but several of these are already
> > requirements which most filesystems don't meet, and other are there
> > to tidy-up interfaces and make locking more straight forward.
>
> As a 2.5 thing it sounds like a very
On Monday February 19, [EMAIL PROTECTED] wrote:
>
>
> On Tuesday, February 20, 2001 11:40:24 AM +1100 Neil Brown
> <[EMAIL PROTECTED]> wrote:
> >
> > When reiserfs came along, it abused this, and re-interpreted the
> > opaque datum to contain information for recalling (locating) an
> >
Hi,
What do you think about the following change?
We currently have the following structure used for registering protocol
handlers as well as bridges, wiretaps etc. (include/linux/netdevice.h):
struct packet_type
{
unsigned short type; /* This is really htons(ether_type). */
struct
> This may seem like a lot, but several of these are already
> requirements which most filesystems don't meet, and other are there
> to tidy-up interfaces and make locking more straight forward.
As a 2.5 thing it sounds like a very sensible path. It will also provide
some of the operations
On Tuesday, February 20, 2001 11:40:24 AM +1100 Neil Brown
<[EMAIL PROTECTED]> wrote:
>
> When reiserfs came along, it abused this, and re-interpreted the
> opaque datum to contain information for recalling (locating) an
> inode - if read_inode2 was defined. I think this is wrong.
>
I
On Sat, Feb 17, 2001 at 09:53:48PM -0700, Eric W. Biederman wrote:
> Peter Samuelson <[EMAIL PROTECTED]> writes:
> > It also sounds like you will be
> > breaking the extremely useful C postulate that, at the ABI level at
> > least, arrays and pointers are equivalent. I can't see *how* you plan
>
Why isn't there a sendfile64?
Felix
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Hi Linus,
Take a look at __lock_page:
static void __lock_page(struct page *page)
{
struct task_struct *tsk = current;
DECLARE_WAITQUEUE(wait, tsk);
add_wait_queue_exclusive(>wait, );
for (;;) {
sync_page(page);
Have you heard anything more on the loop patches? I'm not on the kernel
list anymore. I need to be able to run 2.4 and use the loop devices to
mount cd images?
Ted
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
On Monday February 19, [EMAIL PROTECTED] wrote:
> > I hope to put out a patch set for testing in a day or so and possibly
> > suggest it to Alan for his -ac series. I don't see it going into
> > 2.4.2, but 2.4.3 might be possible if Linus agrees.
>
> Im not interested in a patch that requires
On Mon, Feb 19, 2001 at 04:18:40PM -0800, Ion Badulescu wrote:
> > In my experiments wait_for_cmd timeouts almost always were related to
> > DumpStats command.
> > I think, we need to investigate what time constraints are related to this
> > command.
>
> Nothing documented...
>
> CaT, can you
On Mon, Feb 19, 2001 at 06:58:45PM -0500, Albert D. Cahalan wrote:
> Dieter =?iso-8859- writes:
> > /*
> > * pmap.c: implementation of something like Solaris' /usr/proc/bin/pmap
> > * for linux
>
> I've been planning to implement that tool for procps. So, one way
> or another, it will be
On Mon, 19 Feb 2001 14:49:35 -0800, Andrey Savochkin <[EMAIL PROTECTED]> wrote:
> On Tue, Feb 20, 2001 at 09:21:06AM +1100, CaT wrote:
>>
>> It happened again. Same deal. Once was after a reboot and this time
>> was after a resume. :/
>
> In my experiments wait_for_cmd timeouts almost always
Dieter Nützel wrote:
> * Justification: the formatting available in /proc//maps is less
> * than optimal. It's hard to figure out the size of a mapping from
> * that information (unless you can do 8-digit hex arithmetic in your
> * head) and it's just generally not friendly. Hence this
Dieter =?iso-8859- writes:
> Hello Rik,
>
> there is a nice little toy called "pmap.c" around for several years, now.
> Should we consider?
>
> /*
> * pmap.c: implementation of something like Solaris' /usr/proc/bin/pmap
> * for linux
I've been planning to implement that tool for procps. So,
Hi,
This patch makes page_launder() do actual disk IO
(run_task_queue(_disk)) only if IO was queued in the page freeing
loop.
If we freed enough clean pages without needing do to any disk IO, there is
no need to call run_task_queue(_disk).
--- linux/mm/vmscan.c.orig Mon Feb 19
Hello Rik,
there is a nice little toy called "pmap.c" around for several years, now.
Should we consider?
/*
* pmap.c: implementation of something like Solaris' /usr/proc/bin/pmap
* for linux
*
* Author: Andy Isaacson <[EMAIL PROTECTED]>
* Fri Jun 18 1999
*
* Updated Mon Oct 25 1999
* -
On Mon, 19 Feb 2001, Bill Wendling wrote:
> The use of the ternary operator is superfluous, though...and makes the
> code look ugly IMNSHO :).
What is ugly is that the commitee can not decide if there is going to be
host-side only, device-side only or both-side.
Cheers,
Andre Hedrick
Linux
Also sprach Andre Hedrick:
} On Mon, 19 Feb 2001, Pozsar Balazs wrote:
}
} > from drivers/ide/ide-features.c:
} >
} > /*
} > * All hosts that use the 80c ribbon mus use!
} > */
} > byte eighty_ninty_three (ide_drive_t *drive)
} > {
} > return ((byte) ((HWIF(drive)->udma_four) &&
} >
Hello,
Here's a handy little patch that makes the kernel parse out the ip
address of the nfs server from the bootp root path. Otherwise it's
impossible to boot the kernel without command line options on diskless
workstations (I hate RPL).
-ben
diff -ur
I'm not subscribed to the kernel mailing list, so please cc any replies
to me.
I'm building a firewall on a P133 with 48 MB of memory using RH 7.0,
latest updates, etc. and kernel 2.4.1.
I've built a customized install of RH (~200MB) which I untar onto the
system after building my raid arrays,
> Did you enable eepro100 power management?
>
i tried with and without power managment enabled and it fails either
way, but i have been playing with the setpci command and have
been able to restore all the pci cards/bridges to their original state
and now everything seems to work great,
> It seem obvious that this change in behaviour is isapnptools related, but
> not detecting the whole three IO addresses is an unresolved problem (as of
> 2.2.18, not tried with built-in PnP support in 2.4.x).
Its a bug in the hardware
-
To unsubscribe from this list: send the line "unsubscribe
Hi,
On Tue, Feb 20, 2001 at 09:21:06AM +1100, CaT wrote:
> On Tue, Feb 13, 2001 at 03:14:09PM +1100, CaT wrote:
> > On Tue, Feb 13, 2001 at 09:26:38AM +0800, Andrey Savochkin wrote:
> > > On Sun, Feb 11, 2001 at 10:40:33PM +1100, CaT wrote:
> > > [snip]
> > > > Feb 11 22:30:18 theirongiant
On Mon, Feb 19, 2001 at 03:44:10PM -0800, Dragan Stancevic wrote:
> On Tue, Feb 20, 2001, CaT <[EMAIL PROTECTED]> wrote:
> ;
> ; None. This is before any traffic gets put through it. At worst the
> ; card has the wrong IP for the network but that is not always the case
> ; from memory.
>
> So
On Tue, Feb 20, 2001, CaT <[EMAIL PROTECTED]> wrote:
;
; None. This is before any traffic gets put through it. At worst the
; card has the wrong IP for the network but that is not always the case
; from memory.
So where does that card get the address from, are you doing DHCP?
--
No Kernel
On Mon, 19 Feb 2001, Pozsar Balazs wrote:
> from drivers/ide/ide-features.c:
>
> /*
> * All hosts that use the 80c ribbon mus use!
> */
> byte eighty_ninty_three (ide_drive_t *drive)
> {
> return ((byte) ((HWIF(drive)->udma_four) &&
> #ifndef CONFIG_IDEDMA_IVB
>
On Mon, Feb 19, 2001 at 03:37:02PM -0800, Dragan Stancevic wrote:
> On Tue, Feb 20, 2001, CaT <[EMAIL PROTECTED]> wrote:
> ; > 100% accuracy and so it'll take me a wee while before I decide '
> ; > a... that rocks my boat. it's fixed.'. :)
> ;
> ; It happened again. Same deal. Once
"Eric W. Biederman" wrote:
> No it forbids executing boot roms that way, by a standard pc bios.
> The system BIOS in a PC is normally on the ISA bus which is reached
> across via the PCI bus with a PCI->ISA bridge.
Son of a gun, I missed that... sure enough my PIIX4 docs beside me here
show a
On Mon, 19 Feb 2001, Philipp Rumpf wrote:
> No. If kswapd oopses it's a bug in kswapd (or related code). If keventd
> oopses most likely the broken code is actually the task queue you
> scheduled, which belongs to your driver.
If we're going to detect this case, we might as well just restart
On Tue, Feb 20, 2001, CaT <[EMAIL PROTECTED]> wrote:
; > 100% accuracy and so it'll take me a wee while before I decide '
; > a... that rocks my boat. it's fixed.'. :)
;
; It happened again. Same deal. Once was after a reboot and this time
; was after a resume. :/
What kind of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm having some troubles with a Trident 4DWave NX sound card
(specifically the Hoontech Digital-NX model). I loaded the modules
soundcore.o, ac97_codec.o, and trident.o, in that order, and when I
try to use the devices /dev/dsp and /dev/audio, I
On Tue, Feb 13, 2001 at 03:14:09PM +1100, CaT wrote:
> On Tue, Feb 13, 2001 at 09:26:38AM +0800, Andrey Savochkin wrote:
> > On Sun, Feb 11, 2001 at 10:40:33PM +1100, CaT wrote:
> > [snip]
> > > Feb 11 22:30:18 theirongiant kernel: eepro100: cmd_wait for(0x70) timedout
>with(0x70)!
> >
> >
the TCP code should be "honouring" the link-local MTU in its selection
of MSS.
rick jones
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ
Hi!
Here is a new syscall. With this you can change the owner of a running
procces.
I put the architecture dependent part (syscall NR, and function address)
only to the i386, becouse I'm not familiar with the other arch.
What do you think about it?
I think it's useful, but...
Now I'm writing the
Hi.
For some time up through the testX kernels I used rsync to
update my "dirty" tree after applying the latest patches to the
clean tree. At some point this stopped working (more about that
later) but as new kernels were coming fast at that time I did
not think much of it, assuming that
Jeremy Jackson <[EMAIL PROTECTED]> writes:
> Jaswinder Singh wrote:
>
> > Dear Sirs,
> >
> > Thanks for your help,
> >
> > I see . The biggest negative point of running kernel from ROM is that ROM
> > speed is slow :(
>
> Also, the PCI specification forbids executing code from ROMs over the
Mikulas Patocka <[EMAIL PROTECTED]> writes:
> Imagine that there is specification of mark_buffer_dirty. That
> specification says that
> 1. it may not block
> 2. it may block
>
> In case 1. implementators wouldn't change it to block in stable kernel
> relese because they don't
>BTW, is there really enough common ground between the whole series of
>AIC chips to justify a single huge driver? I know they ship three
>separate NT drivers to cover this range..
The chips are very similar. I think the single driver for Linux is
actually a smaller binary than any of the
from drivers/ide/ide-features.c:
/*
* All hosts that use the 80c ribbon mus use!
*/
byte eighty_ninty_three (ide_drive_t *drive)
{
return ((byte) ((HWIF(drive)->udma_four) &&
#ifndef CONFIG_IDEDMA_IVB
(drive->id->hw_config & 0x4000) &&
#endif /*
On Mon, 19 Feb 2001 [EMAIL PROTECTED] wrote:
> Wakeup does not happen until _enough_ (1/3 of snbuf) of space in sndbuf
> is released, otherwise you will overschedule. So, as soon as
> write() goes to sleep, it will sleep waiting until 1/3 is released.
Of course. Thank you.
> If it is
On Mon, 19 Feb 2001 10:58:36 -0500 (EST),
"Richard B. Johnson" <[EMAIL PROTECTED]> wrote:
>I was unable to use the new kernel because the drivers I need for
>`initrd` all had undefined symbols relating to some high memory stuff.
>This, in spite of the fact that I did:
>
>cp .config ..
>make
On Mon, 19 Feb 2001 16:04:07 + (GMT),
Alan Cox <[EMAIL PROTECTED]> wrote:
>My spinlock based fix has almost no contention and doesnt require 64 processors
>grind to a halt on a big machine just to handle a module list change. Sorry
>I don't think it supports your argument
I am not proposing
>
> Feb 19 19:37:17 delphin kernel: testing the IO APIC...
> Feb 19 19:37:17 delphin kernel:
> Feb 19 19:37:17 delphin kernel: WARNING: unexpected IO-APIC, please mail
> Feb 19 19:37:17 delphin kernel: to [EMAIL PROTECTED]
> Feb 19 19:37:17 delphin kernel:
Russell King wrote:
>
> Albert D. Cahalan writes:
> > The TCP maintainers do not seem to be sadistic bastards hell-bent on
> > breaking your drivers. API changes usually have a good reason.
>
> And when the API does change, like it has between Linux 2.2 and Linux 2.4,
> an email gets sent to
On Mon, 19 Feb 2001, Russell King wrote:
> Philipp Rumpf writes:
> > That still won't catch keventd oopsing though - which I think might happen
> > quite easily in real life.
>
> Maybe we should panic in that case? For example, what happens if kswapd
> oopses? kreclaimd? bdflush? kupdate?
> May-be this is the reason some UNIX vendors seem to love UDI. :)
>
> If you also use SYMBIOS chips, you may give a try with SYM-2. For the
> moment, it replaces only 6 drivers :) as also seems to do, for the moment,
> Justin's AIC7XXX-6, by the way.
>
> The plans seem clear to me. :-)
> Btw,
Albert D. Cahalan writes:
> The TCP maintainers do not seem to be sadistic bastards hell-bent on
> breaking your drivers. API changes usually have a good reason.
And when the API does change, like it has between Linux 2.2 and Linux 2.4,
an email gets sent to this list describing the change of
On Mon, 19 Feb 2001 14:25:39 +0100,
Christoph Hellwig <[EMAIL PROTECTED]> wrote:
>You just reinvented the read-copy-update model
>(http://www.rdrop.com/users/paulmck/rclock/intro/rclock_intro.html)...
>
>The mail proposing that locking model for module unloading is not yet
>in the arvhices,
Dear kernel-developers,
I do not have any experience in kernel programming, but I do have a message
in my /var/log/messages file which advices me to post to this list. This is
the first time for me to visit this list, so don't be too hard too me if this
posting doesn't fit into the common
On Mon, 19 Feb 2001, Peter Samuelson wrote:
> [Justin Gibbs]
> > I've verified the driver's functionality on 25 different cards thus
> > far covering the full range of chips from aic7770->aic7899.
>
> That's very good to hear. I know the temptation of only testing on new
> hardware; that's
Philipp Rumpf writes:
> That still won't catch keventd oopsing though - which I think might happen
> quite easily in real life.
Maybe we should panic in that case? For example, what happens if kswapd
oopses? kreclaimd? bdflush? kupdate? All these have the same problem,
and should probably
On Monday, 19 February 2001, at 14:28:09 -0500,
Bill Nottingham wrote:
> The awe_wave driver in 2.2 looked at the common I/O ports for
> the card if no parameters were specified. The 2.4 driver currently
> does an ISAPnP probe, but doesn't fall back to the previous probing
> behavior, which
Hi.
> I am configuring Bind 9 on Redhat 7 but unable to start the named.
> Here is my /var/log message log:
Read the documentation and you shall notice that you must set a ttl for
each zone, which also your logs state that you have not done ...
// Stefan
-
To unsubscribe from this list: send
> One of these things must happen:
>
> a. follow the specification, even if that makes code slow and contorted
> b. change the specification
> c. ignore the specification
> d. get rid of the specification
>
> Option "a" will not be accepted around here. Sorry.
It should be followed in stable
[Justin Gibbs]
> I've verified the driver's functionality on 25 different cards thus
> far covering the full range of chips from aic7770->aic7899.
That's very good to hear. I know the temptation of only testing on new
hardware; that's why I was concerned.
> Lots of people here at Adaptec look
On Monday 19 February 2001 15:16, you wrote:
> what raid level?
>
Raid 0
> -Tony
> .-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
> Anthony J. Biacco Network Administrator/Engineer
> [EMAIL PROTECTED] Intergrafix Internet Services
>
>
Mikulas Patocka writes:
> Imagine that there is specification of mark_buffer_dirty. That
> specification says that
> 1. it may not block
> 2. it may block
>
> In case 1. implementators wouldn't change it to block in stable kernel
> relese because they don't want to violate the
On Monday 19 February 2001 14:58, Admin Mailing Lists wrote:
> Can anyone give testimonials on a journaled FS on software-raid?
> I'd like to raid-0 2 SCSI 18Gers, adaptec 2940 u2w controller, kernel
> 2.4.x.
> Also pros and cons for reiser-fs/ext3 on this solution would be
> appreciated
>
>
Can anyone give testimonials on a journaled FS on software-raid?
I'd like to raid-0 2 SCSI 18Gers, adaptec 2940 u2w controller, kernel
2.4.x.
Also pros and cons for reiser-fs/ext3 on this solution would be
appreciated
Thanx,
-Tony
The awe_wave driver in 2.2 looked at the common I/O ports for
the card if no parameters were specified. The 2.4 driver currently
does an ISAPnP probe, but doesn't fall back to the previous probing
behavior, which means that users with working module configurations
will have theirs broken on
On Mon, 19 Feb 2001, Henning P . Schmiedehausen wrote:
> And yes, there _is_ IMHO a difference in telling someone on LKM,
> especially someone without deeper knowledge that is lookin for help:
>
> "You're using a non-open source driver, so we can't help you. Please
> ask your vendor for
I caught this one a little bit late, but you might want to take
a peek at the Linux Trace Toolkit:
http://www.opersys.com/LTT
You'll be able to monitor I/O at will.
Best regards,
Karim
> Michael McLeod wrote:
>
> Hello
>
> I am hoping someone can give me a little information or point me
Hi,
I found a bug in the generic floating point emulation code. The glibc
math testcases showed errors for the nearbyint(0.5) test. The problem
is in the _FP_FRAC_SRS_2 macro. The expression to find out if some 1
bits have been shifted out is wrong. Try the _FP_FRAC_SRS_2 macro
with the
ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/
"An innovation a day keeps the monopolist away"
2.4.1-ac19
o Fix second module/exception table race (me)
| I hope ;)
o Additional CPIA usb ident (Adam J Richter)
o
> > > > I suspect part of the problem with commercial driver support on Linux is that
> > > > the Linux driver API (such as it is) is relatively poorly documented
> > >
> > > In-kernel documentation, agreed.
> > >
> > > _Linux Device Drivers_ is a good reference for 2.2 and below.
> >
> > And
> ac97_codec: AC97 Audio codec, vendor id1: 0x4144, id2: 0x5360 (Analog
> Devices AD1885)
> i810_audio: Codec refused to allow VRA, using 48Khz only.
> i810_audio: Found 1 audio device(s).
>
> As seen above, playback is supported only for 48khz samples.
If the codec only supports 48Khz samples
The integrated LAN on Intel boards with i815 chipset
apparently is not fully supported. In latest 2.2.x and 2.4.x,
with the EtherExpress Pro100 driver, after some network traffic,
it locks. The only way I can use the net again is either reboot,
or ifconfig eth0 down; ifconfig eth0 up.
Should this onboard audio work with the i810 driver, in 2.2.x
and 2.4.x ?
The card is detected as ICH2, although the driver supports only ICH.
Intel 810 + AC97 Audio, version 0.17, 17:24:05 Feb 17 2001
PCI: Increasing latency timer of device 00:fd to 64
i810: Intel ICH2 found at
Hello!
> We are implementing an IP stack.
Alan, please, tell me what is wrong. And we will repair this.
The implementation follows RFCs and even relaxes their requirements
in the cases, when they are far from reality.
Alexey
-
To unsubscribe from this list: send the line "unsubscribe
anyone have idea?
I think someone was done before to optimizer AMD K6-2+ CPU in gcc patch.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the
Hello!
> You are right - our sendfile() implementation is broken. I have fixed it
Thank you!
> Investigation shows that the Linux network layer is behaving oddly. It
> seems that we are writing 4096 bytes to a socket. This proceeds in 4096
> byte chunks until the send buffer on the socket is
> * - 2001/01/07 Replace the OPL3 part of CONFIG_SOUND_YMFPCI_LEGACY code with
> *native synthesizer through a playback slot.
>
> It sounds more promising than it is :-(
Non old style OSS synthesizers dont support the legacy /dev/sequencer interface
-
To unsubscribe from this list: send
1 - 100 of 384 matches
Mail list logo
