Alan Cox wrote:
Do you have sort of a 'patch' from your port? I could take this as a
guideline for what has to be changed from 2.2 to 2.4. If I compare the
2.4 driver to the actual 2.2 one, there are far too much differences for
me...
I dontt. Other than comparing the 2.2 and 2.4
At Mon, 9 Apr 2001 22:43:53 -0700 (PDT),
Linus Torvalds wrote:
The ordering is certainly possible, but if it happens,
__down_read_failed() won't actually sleep, because it will notice that the
value is positive and just return immediately. So it will do some
unnecessary work (add itself to
Hi, Cycle Counters,
Linux currently tries to synchronize TSCs for consistent time in SMP
systems. One would not believe what combinations of hardware are tried,
especially for precision timing. Here's a short answer to my asking-
back about a complaint (the kernel is reporting negative time
On Mon, Apr 09 2001, Joao Paulo Martins wrote:
Hi,
I purchase a Promise SuperTrak100 RAID controler and
[snip, SuperTrak not working]
I tried talking to Promise recently to get a sample SuperTrak to
make this work, but no such luck. So bother Promise and ask what
they intend to do
Just how would you do kernel/user CPU time accounting then ? It's
currently done
on every timer tick, and doing it less often would make it useless.
This part is architecture dependent. For S/390 I choose to do a "STCK" on
every
system entry/exit. Dunno if this can be done on other
Its worth doing even on the ancient x86 boards with the PIT. It does
require
some driver changes since
while(time_before(jiffies, we_explode))
poll_things();
no longer works
On S/390 we have a big advantage here. Driver code of this kind does not
exist.
That makes it a lot
Since you're willing to use CMPXCHG in your suggested implementation, would it
make it make life easier if you were willing to use XADD too?
Plus, are you really willing to limit the number of readers or writers to be
32767? If so, I think I can suggest a way that limits it to ~65535 apiece
[EMAIL PROTECTED] (Chip Salzenberg) writes:
AFAIK, Alex Viro's idea of bindable namespaces provides effective
transaction support *ONLY* if there are per-process bindings. With
per-process bindings, each client that opens a connection does so
through a distinct binding; when that client's
Several weeks ago there had been a thread on the pirq assignments of newer VIA
and SiS chipsets ending with everybody happy.
Everybody? Not everybody - there is a small village of chipsets resisting the
advent of 2.4.x :(
The system is a KT133A (MSI's K7T Turbo MS-6330 board)/Duron 700
system.
For me 2.4.3 + aic7xxx-6.1.10 work fine. I just changed the default
bus settle delay from 15000ms to 5000m, and enabled APIC:
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_LOCAL_APIC=y
The machine boots, devices are properly detected (unlike 6.1.8),
CDRW reads and burns fine, CDROM
Hi!
Just how would you do kernel/user CPU time accounting then ? It's currently done
on every timer tick, and doing it less often would make it useless.
Except for machines with very slow timers we really should account time
to processes during context switch instead of sampling on timer
Daniel Phillips writes:
The zeroth block of an indexed directory is the index root. Initially
the index has only one block. The following blocks are normal ext2
directory entry blocks. When the directory grows large enough to fill
all the available entries in the root index block (around
Martin Mares writes:
[lost]
Just how would you do kernel/user CPU time accounting then ?
It's currently done on every timer tick, and doing it less
often would make it useless.
Except for machines with very slow timers we really should account time
to processes during context switch
copy_from_user should probably have something like
(sizeof(agp_segment) * reserve.seg_count)
as it's size argumenbt rather than
GFP_KERNEL
/u2/engler/mc/oses/linux/2.4.3/drivers/char/agp/agpgart_fe.c:882:agpioc_reserve_
wrap: ERROR:SIZE-CHECK:882:882: segment =
On Tue, Apr 10, 2001 at 03:11:05AM -0700, Dawson Engler wrote:
As a side question: is it still true that verify_area's must be done before
any use of __put_user/__get_user/__copy_from_user/etc?
I believe so, at least in generic code.
In architecture specific code (non-i386) it is usually
After 11 months of painstaking work and testing, CML2 1.0.0 is ready for use,
and ready to replace the current kernel-configuration system. You'll
find it at http://www.tuxedo.org/~esr/cml2/. I've made a transition
guide available at http://www.tuxedo.org/~esr/cml2/transition.html.
(Why this
Hello!
Some time ago I had an undefined symbol in kernel compilation (__mul64) It
was sparc architecture, cross compilation on solaris/sparc. I have found
that 64-bit multiplication is in nfs2xdr.c, nfs_xdr_statfsres function. The
multiplication is by nfs_fsinfo-bsize.
For some reason
On Tue, Apr 10, 2001 at 06:41:28AM -0400, Jakub Jelinek wrote:
some architectures don't care at all, because verify_area is a noop
(sparc64).
Why (and how) is this?
--
Petru Paler, mailto:[EMAIL PROTECTED]
http://www.ppetru.net - ICQ: 41817235
-
To unsubscribe from this list: send the line
So, what about on an alpha system. I've asked a few times what I could do,
but you didn't help nor explain what you meant.
From talking to the maintainer of the QLogic driver, it appears
that there is a generic issue with data mapping on the Alpha.
The only way to correct this issue
2.4.4-p1 is the kernel version that i've tried now. no succes with 2.4.3 and
below.
Please see if the 2.4.3-ac version of osb4 works on your box. I need to get
more results on this to know if I got it right
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
So, what about on an alpha system. I've asked a few times what I could do,
but you didn't help nor explain what you meant.
From talking to the maintainer of the QLogic driver, it appears
that there is a generic issue with data mapping on the Alpha.
The only way to correct this issue will
Hi
Unix/Linux have a lot of daemons that have to run as root because they
need to acces some specific data or run special programs. They are
vulnerable as we learn.
Is there any way to have something like an exec call that is
subject to a sudo like permission system? That would run the daemons
On Tue, Apr 10, 2001 at 12:55:29PM +0200, kees wrote:
Unix/Linux have a lot of daemons that have to run as root because they
need to acces some specific data or run special programs. They are
vulnerable as we learn.
Is there any way to have something like an exec call that is
subject to a
interrupting decrementer. (i.e just about any modern chip)
Just how would you do kernel/user CPU time accounting then ? It's currently done
on every timer tick, and doing it less often would make it useless.
On the contrary doing it less often but at the right time massively improves
I purchase a Promise SuperTrak100 RAID controler and
[snip, SuperTrak not working]
I tried talking to Promise recently to get a sample SuperTrak to
make this work, but no such luck. So bother Promise and ask what
they intend to do about it.
I've been talking constructively to promise
I dontt. Other than comparing the 2.2 and 2.4 driver
Surprise, surprise! I just got an email from Patrick Petersen
[EMAIL PROTECTED] with a 2.4 driver I should test
Great.
I'll keep you up to date, and will send you a patch if you like to.
Do let me know and get him to send me a
Hi,
I have a machine running a 2.4.2 kernel with an Adaptec SCSI
board. This worked well, but when I ran into a hang with the 2.4.2
loop device, testing a CD image, I decided to switch to 2.4.3. But
then I get strange error messages during boot, and the machine reacts
(kind of once a day) in a
On Tue, Apr 10 2001, Alan Cox wrote:
I purchase a Promise SuperTrak100 RAID controler and
[snip, SuperTrak not working]
I tried talking to Promise recently to get a sample SuperTrak to
make this work, but no such luck. So bother Promise and ask what
they intend to do about it.
2.4 but then so does IDE DMA for example. The real test would be to run
Justin's 2.2.19 patch driver and see if that works on Alpha.
Sure, I'll try it. I didn't have any luck with the one from 2.2.17 or
2.2.18 on this system.
If the original aic7xxx driver works on your Alpha and
On Tue, 10 Apr 2001, kees wrote:
Hi
Unix/Linux have a lot of daemons that have to run as root because they
need to acces some specific data or run special programs. They are
vulnerable as we learn.
Is there any way to have something like an exec call that is
subject to a sudo like
board. This worked well, but when I ran into a hang with the 2.4.2
loop device, testing a CD image, I decided to switch to 2.4.3. But
then I get strange error messages during boot, and the machine reacts
(kind of once a day) in a very strange way, like programs failing
which never fail.
Just how would you do kernel/user CPU time accounting then ? It's
currently done
on every timer tick, and doing it less often would make it useless.
On the contrary doing it less often but at the right time massively
improves
its accuracy. You do it on reschedule. An rdtsc instruction is
On Mon, Apr 09, 2001 at 11:35:44PM +0100, Alan Cox wrote:
Its worth doing even on the ancient x86 boards with the PIT.
Note that programming the PIT is slw and doing it on every timer
add_timer/del_timer would be a pain.
You only have to do it occasionally.
When you add a
- Original Message -
From: "Alan Cox" [EMAIL PROTECTED]
To: "Alexandru Barloiu Nicolae" [EMAIL PROTECTED]
Cc: "Mark Hahn" [EMAIL PROTECTED];
[EMAIL PROTECTED]
Sent: Tuesday, April 10, 2001 1:00 PM
Subject: Re: Compaq proliant ML-350 - IDE SCSI
2.4.4-p1 is the kernel version that
Jens Axboe wrote:
On Tue, Apr 10 2001, Alan Cox wrote:
I purchase a Promise SuperTrak100 RAID controler and
[snip, SuperTrak not working]
I tried talking to Promise recently to get a sample SuperTrak to
make this work, but no such luck. So bother Promise and ask what
they
On Tue, Apr 10, 2001 at 12:18:03PM +0100, Alan Cox wrote:
interrupting decrementer. (i.e just about any modern chip)
Just how would you do kernel/user CPU time accounting then ? It's currently done
on every timer tick, and doing it less often would make it useless.
On the contrary
Its worth doing even on the ancient x86 boards with the PIT.
Note that programming the PIT is slw and doing it on every timer
add_timer/del_timer would be a pain.
You only have to do it occasionally.
When you add a timer newer than the current one
(arguably
Does not sound very attractive all at all on non virtual machines (I see the point on
UML/VM):
making system entry/context switch/interrupts slower, making add_timer slower, just
to
process a few less timer interrupts. That's like robbing the fast paths for a slow
path.
Measure the number
On Tue, Apr 10, 2001 at 06:47:00AM -0400, Eric S. Raymond wrote:
On 30 March 2001 at the Kernel Summit, Keith Owens and I worked out a
transition schedule with Linus. Keith's rewrite of the makefile system and
my configurator tools are officially slated to replace the present system in
the
which kind of U/K accaounting are you referring to?
are you referring to global changes in world time? are you referring to time
used by a process?
I think the reduction of clock interrupts by a factor of 10 would buy us some
performance margin that could be traded for a slightly more complex
On Mon, 09 Apr 2001, Alan Cox wrote:
Its worth doing even on the ancient x86 boards with the PIT. It does require
some driver changes since
while(time_before(jiffies, we_explode))
poll_things();
no longer works
jiffies could be replaced easily enough w/ a macro
On Tue, Apr 10, 2001 at 03:11:05AM -0700, Dawson Engler wrote:
segment = kmalloc((sizeof(agp_segment) * reserve.seg_count),
GFP_KERNEL);
if (segment == NULL) {
return -ENOMEM;
}
On Tue, 10 Apr 2001, Martin Mares wrote:
Except for machines with very slow timers we really should account time
to processes during context switch instead of sampling on timer ticks.
The current values are in many situations (i.e., lots of processes
or a process frequently waiting for events
On Tue, Apr 10, 2001 at 01:12:14PM +0100, Alan Cox wrote:
Measure the number of clocks executing a timer interrupt. rdtsc is fast. Now
consider the fact that out of this you get KHz or better scheduling
resolution required for games and midi. I'd say it looks good. I agree
And measure the
On Tue, Apr 10, 2001 at 02:04:17PM +0200, Mikulas Patocka wrote:
Adding and removing timers happens much more frequently than PIT tick, so
comparing these times is pointless.
If you have some device and timer protecting it from lockup on buggy
hardware, you actually
send request to
An invocation of hdparm -Tt /dev/sda (id 5) does this:
(scsi1:A:1): 5.000MB/s transfers (5.000MHz, offset 15)
(scsi1:A:6): 20.000MB/s transfers (20.000MHz, offset 15)
(scsi0:A:5): 3.300MB/s transfers
The situation might be clearer if you run with aic7xxx=verbose.
My guess is that the target
On Tue, 10 Apr 2001, David Schleef wrote:
i.e., the TSC, you have to use 8254 timer 0 as both the timebase
and the interval counter -- you end up slowly losing time because
of the race condition between reading the timer and writing a
new interval.
actually, I have an algorithm to fix
Hi,
I have an idea: I have a couple of linux-systems running in a intranet which
is not connected to do outside world in any way. Since they're only used for
calculations for which there is no harm if anyone would tamper with them,
security is not neccessary. The only thing important, is
It's also all interrupts, not only syscalls, and also context switch if you
want to be accurate.
We dont need to be that accurate. Our sample rate is currently so low the
data is worthless anyway
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Tue, 10 Apr 2001, Alan Cox wrote:
Does not sound very attractive all at all on non virtual machines (I see the point
on
UML/VM):
making system entry/context switch/interrupts slower, making add_timer slower,
just to
process a few less timer interrupts. That's like robbing the fast
On Tue, Apr 10, 2001 at 01:36:27PM +0100, Alan Cox wrote:
It's also all interrupts, not only syscalls, and also context switch if you
want to be accurate.
We dont need to be that accurate. Our sample rate is currently so low the
data is worthless anyway
Just without checking on context
Justin:
Ya think very buggy? I checked seagate web page and
unfortunately was unable to find any firmware updates
for the barracuda drives.
Curious tho that this has worked flawlessly for well over a
year with all prior version of linux and win2000 as well.
Also a few other folks seem to
On Tue, Apr 10, 2001 at 08:07:04AM -0400, Mark Salisbury wrote:
which kind of U/K accaounting are you referring to?
are you referring to global changes in world time? are you referring to time
used by a process?
The later.
I think the reduction of clock interrupts by a factor of 10
On Tue, 10 Apr 2001, David Schleef wrote:
This just indicates that the interface needs to be richer -- i.e.,
such as having a "lazy timer" that means: "wake me up when _at least_
N ns have elapsed, but there's no hurry." If waking you up at N ns
is expensive, then the wakeup is delayed until
On Tue, 10 Apr 2001, Andi Kleen wrote:
Also generally the kernel has quite a lot of timers.
are these generaly of the long interval, failure timeout type?
i.e. 5 second device timeouts that are killed before they get executed because
the device didn't timeout? if so, they have no effect
Does not sound very attractive all at all on non virtual machines (I see
the point on
UML/VM):
making system entry/context switch/interrupts slower, making add_timer
slower, just to
process a few less timer interrupts. That's like robbing the fast paths
for a slow path.
The system
On Tue, Apr 10, 2001 at 08:42:33AM -0400, Mark Salisbury wrote:
On Tue, 10 Apr 2001, Andi Kleen wrote:
Also generally the kernel has quite a lot of timers.
are these generaly of the long interval, failure timeout type?
A lot of them are, but not all.
-Andi
-
To unsubscribe from this
Do you think it worth an effort ?
--
Andrey Panin| Embedded systems software engineer
[EMAIL PROTECTED]| PGP key: http://www.orbita1.ru/~pazke/AndreyPanin.asc
PGP signature
AP Do you think it worth an effort ?
One could ask this question for all optimalisations.
In fact; for every project.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
AB 2. Given that otherwise in at least my application (and machine
AB without keyboard and mouse can't be too uncommon) there is *no*
AB entropy otherwise, which is rather easier for a hacker. At least
Put a soundcard in your system and install audio-entropyd.
Works pretty nice.
I Do you
Justin:
Ya think very buggy? I checked seagate web page and
unfortunately was unable to find any firmware updates
for the barracuda drives.
I'm pretty sure you need to be up to at leaset 0005 of
the firmware to stabilize this drive.
Curious tho that this has worked flawlessly for well over
richard offer wrote:
uname does not always provide useful information (cross compiling). Even
if you're building the same ISA, you maybe in a chroot'ed environment.
Can we please not assume that everybody only ever builds native...
Nobody is assuming that. If you're hard enough to do a
Note that you call mod_timer also on each packet received - and in worst
case (which may happen), you end up reprogramming the PIT on each packet.
This just indicates that the interface needs to be richer -- i.e.,
such as having a "lazy timer" that means: "wake me up when _at least_
N ns
Has any one tested the performance of the Tulip or AMD cards (or any other
network card) on any Linux version, with any CPU and any chip-set?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Tue, Apr 10, 2001 at 02:35:52PM +0200, Heusden, Folkert van wrote:
Hi,
I have an idea: I have a couple of linux-systems running in a intranet which
is not connected to do outside world in any way. Since they're only used for
calculations for which there is no harm if anyone would tamper
On Tue, Apr 10, 2001 at 04:10:28PM +0200, Mikulas Patocka wrote:
Timers more precise than 100HZ aren't probably needed - as MIN_RTO is 0.2s
and MIN_DELACK is 0.04s, TCP would hardly benefit from them.
On networking bandwidth shaping and traffic control generally need higher precision
timers.
Mikulas Patocka wrote:
BTW. Why we need to redesign timers at all? The cost of timer interrupt
each 1/100 second is nearly zero (1000 instances on S/390 VM is not common
case - it is not reasonable to degradate performance of timers because of
this).
Timers more precise than 100HZ aren't
At what frame size?.
Thanks
Ofer
-Original Message-
From: Bart Trojanowski [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 10, 2001 4:30 PM
To: Ofer Fryman
Cc: '[EMAIL PROTECTED]'; '[EMAIL PROTECTED]'
Subject: Re: network cards (drivers) performance.
On Tue, 10 Apr 2001, Ofer Fryman
BTW. Why we need to redesign timers at all? The cost of timer interrupt
each 1/100 second is nearly zero (1000 instances on S/390 VM is not common
case - it is not reasonable to degradate performance of timers because of
this).
The cost of the timer interrupts on a single image system is
I used 1024 byte IP packet size (+12 bytes of Ethernet header) under 1500
MTU.
On Tue, 10 Apr 2001, Ofer Fryman wrote:
At what frame size?.
Thanks
Ofer
-Original Message-
From: Bart Trojanowski [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 10, 2001 4:30 PM
To: Ofer Fryman
Is there any syscall implemented to read the kstat structure?
Thanks
Eliel C. Sardaons
-
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
In its current implementation, scsi_unblock_requests() simply
clears host_self_blocked in the SCSI host struct. This means
that either a transaction must complete or a new transaction
be issued before the mid-layer will recognize that it can
run the queues. There is no guarantee that either of
I have two Adaptec 2930CU (ultra narrow) cards. I modified the driver to
make them work in ultra mode.
Can you elaborate on what you had to modify?
Apr 3 23:05:10 Jay kernel: scsi1:0:4:0: Attempting to queue an ABORT message
Please run your system with aic7xxx=verbose and send me the
I've been seeing a lot of complaints about aic7xxx in the 2.4.3 kernel. I
think that people are missing the crucial point: aic7xxx won't compile if
you patch up from 2.4.2, but if you download the complete 2.4.3 tarball,
it compiles fine.
So, I conclude that the patch was created incorrectly,
"AC" == Alan Cox [EMAIL PROTECTED] writes:
I tried talking to Promise recently to get a sample SuperTrak
to make this work, but no such luck. So bother Promise and ask
what they intend to do about it.
AC I've been talking constructively to promise about the i2o on
AC the
the attached patch fixes the ext2-fs filesystem corruption that initially
showed up during stress-tests running on Red Hat's internal testsystems,
and which bug kept us busy for a long time. We suspect that a number of
filesystem corruption bugs reported to l-k were caused by this bug too.
Timers more precise than 100HZ aren't probably needed - as MIN_RTO is 0.2s
and MIN_DELACK is 0.04s, TCP would hardly benefit from them.
There are a considerable number of people who really do need 1Khz resolution.
Midi is one of the example cases. That doesn't mean we have to go to a 1KHz
Hi Eric,
After 11 months of painstaking work and testing, CML2 1.0.0
is ready for use,
and ready to replace the current kernel-configuration system. You'll
find it at http://www.tuxedo.org/~esr/cml2/. I've made a transition
guide available at
I'm currently running a BP6 with a on board HPT366 and a 7200rpm
drive. From what I've seen with my setup at home that 19.51 MB/s
sounds just about right for a hdparm test. When the manual is
refering to the "UDMA 4 66 Mb/s" their talking about the maximum
burst rate for the ATA bus not the max
On 10 Apr 2001, Richard Russon wrote:
VM: Undead swap entry 000bb300
VM: Undead swap entry 00abb300
VM: Undead swap entry 016fb300
Known bug ... unknown cause ;(
http://www.linux-mm.org/bugzilla.shtml has it already listed
regards,
Rik
--
Virtual memory is like a game you can't win;
In its current implementation, scsi_unblock_requests() simply
clears host_self_blocked in the SCSI host struct. This means
that either a transaction must complete or a new transaction
Suppose the queue is unblocked from inside the functions called to process
the request. In that situation
This is my first time sending in a patch to the kernel.
This is a one line fix to the abyss tokenring driver in 2.4.2-ac28
I got this fix from the driver maintainer who said
"I guess I really should send this in to Linus"
I'm just going to go ahead and jump the gun and submit it ;)
---
Hi All
This is quite a long email which I have split in two for those that are
interested problem and background...
---Problem---
Kernel Panic Occured with Messages:
Kernel BUG at highmem.c:155
Invalid Operand With sshd somewhere in the mix.
Unfortunately I did a task dump with SYSRQ
Dunlap, Randy [EMAIL PROTECTED]:
I'd like to see one of the prominent web pages inform
people that Python version x.yy(?) is required to use CML2.
It's in the README. Is that good enough?
--
a href="http://www.tuxedo.org/~esr/"Eric S. Raymond/a
"Boys who own legal firearms
On Mon, 9 Apr 2001, george anzinger wrote:
SodaPop wrote:
I too have noticed that nicing processes does not work nearly as
effectively as I'd like it to. I run on an underpowered machine,
and have had to stop running things such as seti because it steals too
much cpu time, even when
After 11 months of painstaking work and testing, CML2 1.0.0
is ready for use,
and ready to replace the current kernel-configuration system. You'll
find it at http://www.tuxedo.org/~esr/cml2/. I've made a transition
guide available at http://www.tuxedo.org/~esr/cml2/transition.html.
Auditing of the CML1 configuration system reveals that the following entries
in Configure.help are orphans -- that is, they correspond to configuration
symbols not in use in 2.4.3.
The patch following the list garbage-collects the Configure.help file.
Symbols marked 'removed' are removed;
Auditing of the CML1 configuration system reveals that the following entries
in Configure.help are orphans -- that is, they correspond to configuration
symbols not in use in 2.4.3.
Please dont use 2.4.3 for verifying these long term. Its woefully out of date
for non x86 ports and many of
On Mon, Apr 09, 2001 at 07:03:46PM +0300, [EMAIL PROTECTED] wrote:
I have written a test module which closely mirrors what my
code tries to
do(attached below). This is what i get:
PRE_R: old skb:c371ee40 new skb:c371ee30
I guess oldskb-len is =0xc, and the slab allocator packs
This patch removes duplicate help entries.
--- Configure.help 2001/04/10 16:21:18 1.2
+++ Configure.help 2001/04/10 16:26:57
@@ -2074,15 +2074,6 @@
If you want to compile it as a module, say M here and read
Documentation/modules.txt. If unsure, say `N'.
-Packet filtering
* $ from [EMAIL PROTECTED] at "10-Apr: 4:08pm" | sed "1,$s/^/* /"
*
*
* richard offer wrote:
* uname does not always provide useful information (cross compiling). Even
* if you're building the same ISA, you maybe in a chroot'ed environment.
*
* Can we please not assume that everybody only
This patch removes duplicate help entries.
Yep. Already fixed in -ac.
-
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
Hello,
I'm just wondering, whether somebody use this SiS 630 chip (VGA, MODEM, LAN,
etc...). If yes, what is the status of the support in the newest kernel
version? Any help is really appreciated to configure video, and other
drivers...
Thanks for the infos in advance,
Tamas Nagy
-
To
Rik van Riel wrote:
On Mon, 9 Apr 2001, george anzinger wrote:
SodaPop wrote:
I too have noticed that nicing processes does not work nearly as
effectively as I'd like it to. I run on an underpowered machine,
and have had to stop running things such as seti because it steals too
richard offer wrote:
* uname does not always provide useful information (cross compiling). Even
* if you're building the same ISA, you maybe in a chroot'ed environment.
*
* Can we please not assume that everybody only ever builds native...
*
* Nobody is assuming that. If you're hard
Alan Cox [EMAIL PROTECTED]:
Im currently working on getting the arch stuff ready to merge with Linus and
this patch will just make it a nightmare.
I withdraw it, then. Would you please do the renames in your patch?
Those ought to go in, at least.
CONFIG_ARCH_EBSA285
Dunlap, Randy [EMAIL PROTECTED]:
Then the README should be listed (linked) on one of the 2 web pages
above. I can't find it without downloading "CML2 prototype
and documentation," right? I think that it should be
more visible that Python version x.yy(?) is needed, without
having to
For a cPCI card I'm working with...
Cheers.
--- 1.23.1.1/drivers/pci/pci.idsSun Mar 25 13:14:20 2001
+++ 1.25/drivers/pci/pci.idsMon Apr 9 11:46:36 2001
@@ -920,6 +920,7 @@
ac51 PCI1420
ac52 PCI1451 PC card Cardbus Controller
ac53 PCI1421 PC card
On Thu, Apr 05, 2001 at 10:52:28PM +0200, Juan wrote:
Tim Waugh escribi:
Could you build a kernel without SMP support and see if the problem
still happens?
Without SMP support, the machine doesn't hang but I can't load the ppa
module.
See messages below.
[...]
[root@localhost /root]#
Alan Cox [EMAIL PROTECTED]:
Im currently working on getting the arch stuff ready to merge with Linus and
this patch will just make it a nightmare.
I withdraw it, then. Would you please do the renames in your patch?
Those ought to go in, at least.
CONFIG_ARCH_EBSA285
1 - 100 of 437 matches
Mail list logo
