On Tue, Apr 05, 2005 at 09:55:06AM +0800, Li Shaohua wrote:
On Mon, 2005-04-04 at 23:33, Nathan Lynch wrote:
No. It should make zero difference to the scheduler whether the play
dead cpu hotplug or physical hotplug is being used.
Keeping some fields like 'cpu_load' are meanless for a
On Tue, 5 Apr 2005 17:33:59 -0700 (PDT), Christoph Lameter [EMAIL
PROTECTED] said:
Christoph Which benchmark would you recommend for this?
I don't know about recommend, but I think SPECweb, SPECjbb,
the-UNIX-multi-user-benchmark-whose-name-I-keep-forgetting, and in
general anything that
On Tue, Apr 05, 2005 at 11:46:41AM -0400, Benjamin LaHaise wrote:
On Mon, Apr 04, 2005 at 01:56:35PM -0400, Trond Myklebust wrote:
IOW: the current semaphore implementations really all need to die, and
be replaced by a single generic version to which it is actually
practical to add new
On Tue, 05 Apr 2005 21:48:22 PDT, David Mosberger wrote:
On Tue, 5 Apr 2005 17:33:59 -0700 (PDT), Christoph Lameter [EMAIL
PROTECTED] said:
Christoph Which benchmark would you recommend for this?
I don't know about recommend, but I think SPECweb, SPECjbb,
On Tue, Apr 05, 2005 at 09:20:57PM -0400, Trond Myklebust wrote:
ty den 05.04.2005 Klokka 11:46 (-0400) skreiv Benjamin LaHaise:
I can see that goal, but I don't think introducing iosems is the right
way to acheive it. Instead (and I'll start tackling this), how about
factoring out the
On April 5, 2005 09:22 pm, Berck E. Nash wrote:
2.6.12-rc2-mm1 fails to build for me with the following error:
arch/i386/lib/mmx.c:374: error: conflicting types for `mmx_clear_page'
include/asm/mmx.h:11: error: previous declaration of `mmx_clear_page'
make[1]: *** [arch/i386/lib/mmx.o] Error
On Tue, 2005-04-05 at 06:13 +0200, Ingo Molnar wrote:
* Lee Revell [EMAIL PROTECTED] wrote:
I can trigger latencies up to ~1.1 ms with a CVS checkout. It looks
like inside ext3_try_to_allocate_with_rsv, we spend a long time in this
loop:
ext3_test_allocatable
building this sucker as a module caused grief.
drivers/net/chelsio/cxgb2.c:113: error: `__mod_pci_device_table' aliased
to external symbol `t1_pci_tbl'.
This seems to do the trick. (untested beyond compile)
Signed-off-by: Dave Jones [EMAIL PROTECTED]
Dave
---
* Nick Piggin [EMAIL PROTECTED] wrote:
This is Suresh's patch with some modifications.
Remove degenerate scheduler domains during the sched-domain init.
actually, i'd suggest to not do this patch. The point of booting with a
CONFIG_NUMA kernel on a non-NUMA box is mostly for testing, and
* Ingo Molnar [EMAIL PROTECTED] wrote:
* Nick Piggin [EMAIL PROTECTED] wrote:
2/5
The previous patch fixed the last 2 places that directly access a
runqueue's sched-domain and assume it cannot be NULL.
We can now use a NULL domain instead of a dummy domain to signify
no
* Nick Piggin [EMAIL PROTECTED] wrote:
2/5
The previous patch fixed the last 2 places that directly access a
runqueue's sched-domain and assume it cannot be NULL.
We can now use a NULL domain instead of a dummy domain to signify
no balancing is to happen. No functional changes.
* Nick Piggin [EMAIL PROTECTED] wrote:
3/5
The fundamental problem that Suresh has with balance on exec and fork
is that it only tries to balance the top level domain with the flag
set.
This was worked around by removing degenerate domains, but is still a
problem if people want to start
With nmi_watchdog=1, I got random Oopses (Unable to handle kernel
paging request, not by the NMI oopser) from many processes.
It is not happend with -rc1.
The following change fixes this problem. but I'm not familiar with
these area. If anyone wants more information, let me know.
---
On Tue, 2005-04-05 at 06:13 +0200, Ingo Molnar wrote:
* Lee Revell [EMAIL PROTECTED] wrote:
I can trigger latencies up to ~1.1 ms with a CVS checkout. It looks
like inside ext3_try_to_allocate_with_rsv, we spend a long time in this
loop:
We have not modify the reservation create
This allows the i386 architecture to be built on a system with a biarch
compiler that defaults to x86-64, merely by specifying ARCH=i386.
As previously discussed, this uses the equivalent logic to the ppc port.
-hpa
Signed-Off-By: H. Peter Anvin [EMAIL PROTECTED]
Index:
Hello, James.
James Bottomley wrote:
On Fri, 2005-04-01 at 14:25 +0900, Tejun Heo wrote:
Ah.. with later requeue path consolidation patches, all requests get
their sense buffer cleared during requeueing, which, IMHO, is more
logical. Moving scsi_init_cmd_errh() should come after the patch.
Dear friend,
I am Patrick Umtanta, an accountant with the ministry
of
Energy and natural resources South Africa, presently
we discovered the sum of 19.6 million
British pounds sterling, floating in our suspense
Account.
This money as a matter of fact was an over invoiced
Contract payment
On Sun, Apr 03, 2005 at 12:57:28PM -0700, Joel Becker wrote:
Folks,
I humbly submit configfs. With configfs, a configfs
config_item is created via an explicit userspace operation: mkdir(2).
It is destroyed via rmdir(2). The attributes appear at mkdir(2) time,
and can be read or
James Morris [EMAIL PROTECTED] wrote:
n Mon, 4 Apr 2005, Andrew Morton wrote:
I got this on a dual P4 Xeon with HT. If anyone wants more information,
let me know.
.config, please..
#
# Automatically generated make config: don't edit
# Linux kernel version:
Paul Jackson [EMAIL PROTECTED] writes:
We already expose the SLIT table node distances (using SN2 specific
/proc files today, others are working on an arch-neutral mechanism).
There is already an arch neutral mechanism in sysfs, see
/sys/devices/system/node/node*/distance
That should be
the crashes below happen when PAGEALLOC is enabled. It's this
instruction:
movb OLDSS(%esp), %ah
OLDSS is 0x38, esp is f4f83fc8, OLDSS(%esp) is thus f4f84000, which
correctly creates the PAGEALLOC pagefault. esp is off by 4 bytes?
it could be the ESP-16-bit-corruption patch causing
On Tue, 2005-04-05 at 01:05 -0400, James Morris wrote:
Evgeniy,
Please send networking patches to [EMAIL PROTECTED]
It was sent there two times.
Your connector code (under drivers/connector) is now in the -mm tree and
as far as I can tell, has not received any review from the network
Ingo Molnar [EMAIL PROTECTED] wrote:
the crashes below happen when PAGEALLOC is enabled. It's this
instruction:
movb OLDSS(%esp), %ah
OLDSS is 0x38, esp is f4f83fc8, OLDSS(%esp) is thus f4f84000, which
correctly creates the PAGEALLOC pagefault. esp is off by 4 bytes?
it
On Tue, 2005-04-05 at 01:10 -0400, James Morris wrote:
On Tue, 5 Apr 2005, James Morris wrote:
A few questions:
Also, please allow cn_add_callback() allow it to be passed a NULL
callback function, so the caller doesn't pass in a dummy function and your
code doesn't waste time dealing
* Ingo Molnar [EMAIL PROTECTED] wrote:
it could be the ESP-16-bit-corruption patch causing this, or it could
be an already existing latent bug getting triggered now: normally only
iret accesses the OLDSS, and we fix any iret faults up, but now that
we explicitly access %esp the esp bug
* Andrew Morton [EMAIL PROTECTED] wrote:
Do you have nmis enabled?
yeah ...
call do_nmi
- jmp restore_all
+ jmp restore_nocheck
and i was about to take a closer look at the NMI path :-)
Ingo
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
i have released the -V0.7.44-00 Real-Time Preemption patch, which can be
downloaded from the usual place:
http://redhat.com/~mingo/realtime-preempt/
this is a merge of -43-08 to 2.6.12-rc2.
http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.11.tar.bz2
* Andrew Morton [EMAIL PROTECTED] wrote:
From: Akinobu Mita [EMAIL PROTECTED]
With nmi_watchdog=1, I got random Oopses (Unable to handle kernel
paging request, not by the NMI oopser) from many processes. It is not
happend with -rc1.
The following change fixes this problem.
this
On Tue, Apr 05, 2005 at 11:03:16AM +0400, Evgeniy Polyakov wrote:
I received comments and feature requests from Herbert Xu and Jamal Hadi
Salim,
almost all were successfully resolved.
Please do not construe my involvement in these threads as endorsement
for this system.
In fact to this day
- Nobody said anything about the PM resume and DRI behaviour in
2.6.12-rc1-mm4. So it's all perfect now?
Well the DRI is, both reports of bugs have been fixed :-), the bug
should be closed on bugs.kernel.org I think, and it looks rock solid
on my box both FC3 and Debian sarge..
Dave.
-
To
Andi wrote:
There is already an arch neutral mechanism in sysfs, see
/sys/devices/system/node/node*/distance
Excellent - thank-you.
But of course SLIT doesn't know anything about cache latencies.
Of course. Though SLIT does know about basic node distances, which
tend to correlate with cache
Oleg Nesterov:
o x86: fix ESP corruption CPU bug (take 2)
I don't even absolutely understand what this patch does :)
I only send a very minor fix on top of Stas Sergeev's patch.
Oleg.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
On Mon, Apr 04, 2005 at 04:17:45PM -0500, James Bottomley wrote:
OK, I sent the patch off to Andrew. To complete the original problem,
the attached is the patch that uses it in the parisc lasi driver
(although, actually, it sets up 53c700 to work everywhere including BE
on a LE system).
I
Andrew Morton wrote:
+sched-remove-unnecessary-sched-domains.patch
+sched-improve-pinned-task-handling-again.patch
[snip]
CPU scheduler updates
It is no problem that you picked these up for testing. But
don't merge them yet, please.
Suresh's underlying problem with the unnecessary sched domains
* Ingo Molnar [EMAIL PROTECTED] wrote:
* Andrew Morton [EMAIL PROTECTED] wrote:
From: Akinobu Mita [EMAIL PROTECTED]
With nmi_watchdog=1, I got random Oopses (Unable to handle kernel
paging request, not by the NMI oopser) from many processes. It is not
happend with -rc1.
On Tue, 2005-04-05 at 01:10 -0400, Herbert Xu wrote:
On Tue, Apr 05, 2005 at 11:03:16AM +0400, Evgeniy Polyakov wrote:
I received comments and feature requests from Herbert Xu and Jamal Hadi
Salim,
almost all were successfully resolved.
Please do not construe my involvement in these threads
On Mon, 4 Apr 2005 22:44:09 -0700 David S. Miller [EMAIL PROTECTED] wrote:
I have no idea how a bug like this lasted so long.
Probably because very few programs pass sigevents into the kernel ...
- memset(event, 0, sizeof(*event));
+ memset(event, 0, sizeof(*event));
Blush :-)
--
On Mon, Apr 04, 2005 at 10:59:32PM +0200, Jesper Juhl wrote:
Hi Steve,
More fs/cifs/ cleanups for you. This time for asn1.c
Btw, shouldn't asn1.c move to lib/?
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
Hi,
I'm porting linux on an embedded system based on MIPS proc. I've
encountered several
problems and one of these is related to the physical memory which
doesn't start to 0.
This is actually not a big issue if code that makes physical address
convertions uses the
appropriate macros that do the
On Mon, Apr 04, 2005 at 11:14:16PM -0700, H. Peter Anvin wrote:
This allows the i386 architecture to be built on a system with a biarch
compiler that defaults to x86-64, merely by specifying ARCH=i386.
As previously discussed, this uses the equivalent logic to the ppc port.
Given that the
On Tue, 5 Apr 2005, Christoph Hellwig wrote:
Date: Tue, 5 Apr 2005 08:35:59 +0100
From: Christoph Hellwig [EMAIL PROTECTED]
To: Jesper Juhl [EMAIL PROTECTED]
Cc: Steve French [EMAIL PROTECTED], Steven French [EMAIL PROTECTED],
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] cifs:
On Sat, Apr 02, 2005 at 09:40:39PM -0600, James Bottomley wrote:
On Sun, 2005-04-03 at 04:10 +0100, Matthew Wilcox wrote:
SPARC64 can do it in the PTEs, but we just use raw physical
addresses in our I/O accessors, and in those load/store instructions
we can specify the endianness.
Andrew Morton a écrit :
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/
Hi Andrew,
printk timing seems broken.
It always shows [ 0.00] on my Compaq Evo N600c.
dmesg and config attached.
- Nobody said anything about the PM resume and DRI behaviour in
On Tue, Apr 05, 2005 at 12:05:24AM -0700, Andrew Morton wrote:
+officially-deprecate-register_ioctl32_conversion.patch
deprecate a compat function (mainly affects DRI)
Those DRI callers aren't in mainline but introduced in bk-drm.patch,
looks like the DRI folks need beating with a big
On Tue, 5 Apr 2005, Esben Nielsen wrote:
I'm sure a lot of the yield() users could be converted to
schedule_timeout(), some of the users i saw were for low memory conditions
where we want other tasks to make progress and complete so that we a bit
more free memory.
Easy, but damn
On Tue, 5 Apr 2005, Li Shaohua wrote:
On Tue, 2005-04-05 at 03:10, Zwane Mwaikambo wrote:
On Mon, 4 Apr 2005, Li Shaohua wrote:
linux-2.6.11-root/arch/i386/kernel/smpboot.c |6 ++
linux-2.6.11-root/arch/i386/kernel/sysenter.c | 10 ++
* Ingo Molnar [EMAIL PROTECTED] wrote:
this fixed my crashes too.
spoke too soon - they still trigger even with the patch applied.
the patch below fixes the crash, it was related to CONFIG_PREEMPT.
Ingo
--
fix entry.S crash with PREEMPT+PAGEALLOC
Signed-off-by: Ingo Molnar
On Tue, 5 Apr 2005 17:37:24 +1000
Stephen Rothwell [EMAIL PROTECTED] wrote:
On Mon, 4 Apr 2005 22:44:09 -0700 David S. Miller [EMAIL PROTECTED] wrote:
I have no idea how a bug like this lasted so long.
Probably because very few programs pass sigevents into the kernel ...
Perhaps, but
Hi,
I am having a little trouble with inotify 0.22. Previous version worked w/o
trouble (even with nvidia and nvsound loaded) with 2.6.12-rc1-kb2 and gamin
Now I use 2.6.12-rc2 with inotify 0.22 and got this after a few minutes of
uptime (compiling some stuff):
Apr 5 09:40:43 tachyon Unable to
* Nick Piggin [EMAIL PROTECTED] wrote:
Andrew Morton wrote:
+sched-remove-unnecessary-sched-domains.patch
+sched-improve-pinned-task-handling-again.patch
[snip]
CPU scheduler updates
It is no problem that you picked these up for testing. But
don't merge them yet, please.
almost
Oleg Nesterov [EMAIL PROTECTED] wrote:
Oleg Nesterov:
o x86: fix ESP corruption CPU bug (take 2)
I don't even absolutely understand what this patch does :)
I only send a very minor fix on top of Stas Sergeev's patch.
I'm suspecting a problem in the reporting scripts. The patch had:
Andrew Morton a écrit :
Brice Goglin [EMAIL PROTECTED] wrote:
Andrew Morton a écrit :
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/
Hi Andrew,
printk timing seems broken.
It always shows [ 0.00] on my Compaq Evo N600c.
What sort of CPU does that
Brice Goglin [EMAIL PROTECTED] wrote:
Andrew Morton a écrit :
Brice Goglin [EMAIL PROTECTED] wrote:
Andrew Morton a écrit :
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/
Hi Andrew,
printk timing seems broken.
It always shows [
On Tue, 2005-04-05 at 11:34 +0400, Evgeniy Polyakov wrote:
On Tue, 2005-04-05 at 01:10 -0400, Herbert Xu wrote:
In fact to this day I still don't understand what problems this thing is
meant to solve.
Hmm, what else can I add to my words?
May be checking the size of the code needed to
Andrew Morton a écrit :
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/
- Nobody said anything about the PM resume and DRI behaviour in
2.6.12-rc1-mm4. So it's all perfect now?
I'm sorry, I did not follow this PM resume broken thread.
But, suspend to
Christoph Hellwig [EMAIL PROTECTED] wrote:
(btw, could you please add to all patches who's responsible for them,
bk-audit.patch doesn't tell)
It's supposed to, but if I have to fix rejects and refresh the patch, I
lose that info. Right now, bk-audit stomps on bk-ia64, so we lost the info.
bk-audit.patch
This introduces various AUDIT_ARCH numerical constants, which is a blatantly
stupid idea. We already have a way to uniquely identify architectures, and
that's the ELF headers, no need for another parallel namespace.
(btw, could you please add to all patches who's responsible
Brice Goglin [EMAIL PROTECTED] wrote:
Andrew Morton a écrit :
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/
Hi Andrew,
printk timing seems broken.
It always shows [ 0.00] on my Compaq Evo N600c.
What sort of CPU does that thing have?
Christoph Hellwig wrote:
Given that the same logic applies to various other ports maybe it should
go into a common Makefile fragment?
Alas, the *details* are different for each architecture.
-hpa
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a
* Brice Goglin [EMAIL PROTECTED] wrote:
Andrew Morton a écrit :
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/
Hi Andrew,
printk timing seems broken.
It always shows [ 0.00] on my Compaq Evo N600c.
could you send the full bootlog (starting
Hi,
Andrew Morton wrote:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/
- x86 NMI handling seems to be bust in 2.6.12-rc2. Try using
`nmi_watchdog=0' if you experience weird crashes.
- The possible kernel-timer related hangs might possibly be fixed. We
On Mon, 2005-04-04 at 23:19 +0200, Sven Luther wrote:
I am only saying that the tg3.c and other file are under the GPL, and
that the firmware included in it is *NOT* intented to be under the
GPL, so why not say it explicitly ?
I don't think anyone here has disagreed. What almost everyone has
Ingo Molnar a écrit :
* Brice Goglin [EMAIL PROTECTED] wrote:
Andrew Morton a écrit :
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/
Hi Andrew,
printk timing seems broken.
It always shows [ 0.00] on my Compaq Evo N600c.
could you send the full
On Apr 4, 2005, at 10:57 PM, Al Viro wrote:
On Mon, Apr 04, 2005 at 10:30:52PM +0200, Renate Meijer wrote:
When used improperly. The #define Al Viro objected to, is
objectionable. It's highly
misleading, as Mr. Viro pointed out. I fail to see where he made
comments on stdint.h
as such.
Comments on
On Apr 3, 2005 11:56 PM, Andrew Morton [EMAIL PROTECTED] wrote:
Mathieu Bérard [EMAIL PROTECTED] wrote:
Hi,
I get a 100% reproductible oops while booting linux 2.6.12-rc1-mm4.
(Everyting run smoothly using 2.6.11-mm1)
It seems to be related with mounting a reiserfs3 filesystem.
It
Hi,
On Tuesday, 5 of April 2005 09:05, Andrew Morton wrote:
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12-rc2/2.6.12-rc2-mm1/
- x86 NMI handling seems to be bust in 2.6.12-rc2. Try using
`nmi_watchdog=0' if you experience weird crashes.
- The possible
Hello there,
After 2½ year I stumbled over this thread:
On Wed, 2002-08-21 at 13:23, Alan Cox wrote:
2.5 propses including the ability to set the %age between the 0% of
mode 3, the 50 of mode 2 and upwards to things relevant in some
embedded system cases. So for 2.6 you will be able to tune it in
2.6.12-rc1 compiles and runs perfectly.
gcc version 2.95.3 20010315 (release)
CC [M] drivers/usb/class/cdc-acm.o
In file included from drivers/usb/class/cdc-acm.c:63:
include/linux/usb_cdc.h:117: field `bDetailData' has incomplete type
make[3]: *** [drivers/usb/class/cdc-acm.o] Error 1
On Mon, 2005-04-04 at 23:33, Nathan Lynch wrote:
I don't understand why this is needed at all. It looks like a fair
amount of code from do_exit is being duplicated here.
Yes, exactly. Someone who understand do_exit please help clean up the
code. I'd like to remove the idle thread,
On Mon, 2005-04-04 at 23:51 -0500, Dmitry Torokhov wrote:
On Monday 04 April 2005 23:23, Jan Harkes wrote:
On Mon, Apr 04, 2005 at 12:17:46PM -0700, Greg KH wrote:
On Mon, Apr 04, 2005 at 08:27:53PM +0200, Sven Luther wrote:
Mmm, probably that 2001 discussion about the keyspan firmware,
On Tue, Apr 05, 2005 at 09:19:24AM +0100, Ian Campbell wrote:
On Mon, 2005-04-04 at 23:19 +0200, Sven Luther wrote:
I am only saying that the tg3.c and other file are under the GPL, and
that the firmware included in it is *NOT* intented to be under the
GPL, so why not say it explicitly ?
On Apr 5, 2005 5:44 PM, Christoph Hellwig [EMAIL PROTECTED] wrote:
On Tue, Apr 05, 2005 at 12:05:24AM -0700, Andrew Morton wrote:
+officially-deprecate-register_ioctl32_conversion.patch
deprecate a compat function (mainly affects DRI)
Those DRI callers aren't in mainline but introduced
Hello,
I've problems with IrDA - when debug is off, I'm getting oops for obvious
reason...
(I don't have a log, this is just rewrite from screen:
EIP: irda_device_set_media_busy+0x15/0x40 [irda]
ali_ircc_sir_receive+0x4a/0x70
ali_ircc_sir_interrupt+0x66/0x70
ali_ircc_interrupt+0x5e/0x80
.
)
Christoph Hellwig writes:
Those DRI callers aren't in mainline but introduced in bk-drm.patch,
looks like the DRI folks need beating with a big stick..
Settle down Christoph, the compat_ioctl method is less than 3 months
old, has only been in one official 2.6.x release, and isn't documented
at
On Tue, Apr 05, 2005 at 07:11:26PM +1000, Paul Mackerras wrote:
Christoph Hellwig writes:
Those DRI callers aren't in mainline but introduced in bk-drm.patch,
looks like the DRI folks need beating with a big stick..
Settle down Christoph, the compat_ioctl method is less than 3 months
On Apr 4, 2005, at 11:49 PM, Kyle Moffett wrote:
On Apr 04, 2005, at 17:25, Richard B. Johnson wrote:
I don't find stdint.h in the kernel source (up to 2.6.11). Is this
going to be a new addition?
Uhh, no. stdint.h is part of glibc, not the kernel.
It would be very helpful to start using the
Dave Airlie writes:
Paulus these look like your patches care to update them with the new
method of doing stuff..
What are we going to do about the DRM CVS? Change it to the new way
and break everyone running 2.6.10 or earlier, or leave it at the old
way that will work for people with distro
On Mon, 2005-04-04 at 16:02 -0400, Robert Love wrote:
Hi,
Below, find inotify 0.22, against 2.6.12-rc1.
Will this be included in mainline anytime soon? Kernel side seems to be
working great, and I think all issues was addressed.
The only real issues currently is with the gamin backend, but
Hi!
You have a few things here that can easily conflict, and that will be
developed at different paces. I like the direction that it's going, but
how do you intend to do it gradually. I.e. what to do first?
I think the first step would be for us to all agree on a design, whether
it be
Paulus these look like your patches care to update them with the new
method of doing stuff..
What are we going to do about the DRM CVS? Change it to the new way
and break everyone running 2.6.10 or earlier, or leave it at the old
way that will work for people with distro kernels, and
On Tue, 5 Apr 2005, Ingo Molnar wrote:
* Esben Nielsen [EMAIL PROTECTED] wrote:
Now the question is, who will fix it? Preferably the maintainers, but I
don't know how much of a priority this is to them. I don't have the time
now to look at this and understand enough about the code
Btw, some more comments on the 32bit compat code in drm:
- instead of set_fs co and passing kernel addresses to drm_ioctl
please use compat_alloc_user_space()
- this:
+ifeq ($(CONFIG_COMPAT),y)
+drm-objs+= drm_ioc32.o
+radeon-objs += radeon_ioc32.o
+endif
should be written as
On Tue, 2005-04-05 at 10:32 +0200, Sven Luther wrote:
On Tue, Apr 05, 2005 at 09:19:24AM +0100, Ian Campbell wrote:
On Mon, 2005-04-04 at 23:19 +0200, Sven Luther wrote:
I am only saying that the tg3.c and other file are under the GPL, and
that the firmware included in it is *NOT*
On Tue, Apr 05, 2005 at 09:49:25AM +0100, Ian Campbell wrote:
I don't think you did get a rejection, a few people said that _they_
weren't going to do it, but if you want to then go ahead. I think people
are just fed up of people bringing up the issue and then failing to do
anything about it
On Tue, 2005-04-05 at 19:20 +1000, Paul Mackerras wrote:
Dave Airlie writes:
Paulus these look like your patches care to update them with the new
method of doing stuff..
What are we going to do about the DRM CVS? Change it to the new way
and break everyone running 2.6.10 or earlier, or
Hi Jan,
Mmm, probably that 2001 discussion about the keyspan firmware, right ?
http://lists.debian.org/debian-legal/2001/04/msg00145.html
Can you summarize the conclusion of the thread, or what you did get
from it,
please ?
That people didn't like the
On Sun, 2005-01-16 at 22:11, Al Viro wrote:
On Sun, Jan 16, 2005 at 01:42:09PM -0500, J. Bruce Fields wrote:
On Sun, Jan 16, 2005 at 06:06:56PM +, Al Viro wrote:
On Sun, Jan 16, 2005 at 11:02:13AM -0500, J. Bruce Fields wrote:
On Thu, Jan 13, 2005 at 10:18:51PM +, Al Viro wrote:
On Tue, Apr 05, 2005 at 07:44:38PM +1000, Paul Mackerras wrote:
Christoph Hellwig writes:
- the magic CONFIG_COMPAT changes for SHM handles should only be done when
a module is set. CONFIG_COMPAT is set for mostly 64bit systems that can
run 32bit code and drm shouldn't behave
On Thu, 2005-03-31 at 12:11 -0500, Lee Revell wrote:
Didn't you ever look up what a ulimit is?
ofcourse i did. I just think that ulimit (or other userspace tools)
should be used to *raise* the limit if you need more. Not the reverse.
If you consider your distro's default ulimits unreasonable,
Ingo Molnar writes:
* Ingo Molnar [EMAIL PROTECTED] wrote:
this fixed my crashes too.
spoke too soon - they still trigger even with the patch applied.
the patch below fixes the crash, it was related to CONFIG_PREEMPT.
Ingo
--
fix entry.S crash with
Christoph Hellwig writes:
Please make it a module option so it doesn't regress everyone for your
specific needs.
Sorry, I don't follow you.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Christoph Hellwig writes:
It's documented where the other filesystem entry points are documented.
Which is?
$ grep -r compat_ioctl Documentation
Documentation/filesystems/Locking: long (*compat_ioctl) (struct file *,
unsigned int, unsigned long);
Hi all,
I wonder whether anyone could use the pktcddvd device without killing
random jobs (due to sudden out of memory or better memory leaks in
pktcddvd) and finally a complete freeze of the machine ?
To reproduce just create an udf filesystem on some dvdrw, mount it rw
and copy some large file
On Tue, 2005-04-05 at 11:11 +0200, Christoph Hellwig wrote:
On Tue, Apr 05, 2005 at 09:49:25AM +0100, Ian Campbell wrote:
I don't think you did get a rejection, a few people said that _they_
weren't going to do it, but if you want to then go ahead. I think people
are just fed up of people
On Tue, 2005-04-05 at 11:11 +0200, Christoph Hellwig wrote:
On Tue, Apr 05, 2005 at 09:49:25AM +0100, Ian Campbell wrote:
I don't think you did get a rejection, a few people said that _they_
weren't going to do it, but if you want to then go ahead. I think people
are just fed up of people
On Tue, Apr 05, 2005 at 11:28:07AM +0200, Arjan van de Ven wrote:
I think they will be accepted if they first introduce a transition
period where tg3 will do request_firmware() and only use the built-in
firmware if that fails.
Fine with me.
Second step is to make the built-in firmware a
Hello Jeff, ...
If i can believe what i see in :
http://linux.bkbits.net:8080/linux-2.6/anno/drivers/net/[EMAIL
PROTECTED]|src/|src/drivers|src/drivers/net|related/drivers/net/tg3.c|[EMAIL
PROTECTED]
(which may or may not be correct and complete, since i am not really familiar
with bk and
On Tue, Apr 05, 2005 at 10:30:47AM +0100, Ian Campbell wrote:
On Tue, 2005-04-05 at 11:11 +0200, Christoph Hellwig wrote:
On Tue, Apr 05, 2005 at 09:49:25AM +0100, Ian Campbell wrote:
I don't think you did get a rejection, a few people said that _they_
weren't going to do it, but if you
Christoph Hellwig writes:
E.g. on my ia64 box CONFIG_COMPAT is set because I have support compiled
in for running i386 apps. But I don't want dri to hand out 32bit handles
everywhere just because of that, because I most certainly won't be running
i386 OpenGL apps.
The handle for a _DRM_SHM
E.g. on my ia64 box CONFIG_COMPAT is set because I have support compiled
in for running i386 apps. But I don't want dri to hand out 32bit handles
everywhere just because of that, because I most certainly won't be running
i386 OpenGL apps.
It doesn't actually matter what size the handles
601 - 700 of 812 matches
Mail list logo
