When I update my kernel to 2.6.20-rc6, I find I can not move the map
smoothly in the Google Earth (V4).
I do not try any test on this issue. just put it to maillist.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majord
On Tuesday 30 January 2007 18:16, Jan Kasprzak wrote:
> Hello,
>
> I have a Tyan h1000E (S3970) dual-socket board, with two
> dual-core AMD Athlon 2210 CPUs (4 cores total). The problem is
> that the kernel apparently cannot detect the SMP configuration
> (after boot, /proc/cpuinfo lis
On Wed, 31 Jan 2007, Nick Piggin wrote:
> Robert P. J. Day wrote:
> > On Tue, 30 Jan 2007, Nick Piggin wrote:
> >
> >
> > > Robert P. J. Day wrote:
> > >
> > > > Add the inline function "is_power_of_2()" to log2.h, where the value
> > > > zero is *not* considered to be a power of two.
> > >
> > >
akuster <[EMAIL PROTECTED]> writes:
> My apologies, I cc'd the wrong list the first time around.
>
> - Armin
> ---
>
> Fastpoweroff default profile driver
Why don't you just call the existing reboot(2)? I've had a simple
C program that does a very fast poweroff (or reboot) forever
and it works
Andrey Borzenkov <[EMAIL PROTECTED]> writes:
> Will it work with netconsole too? COM port is often missing in notebooks
> today.
It will work with some luck with firescope (in the worst case you
might need to disable suspend in ochi1394). Many laptops have firewire
ports.
ftp://ftp.firstfloor.or
kbuild: correctly skip tilded backups in localversion files
Tildes as in path as in filenames are handled correctly now.
Definition of `space' was removed, scripts/Kbuild.include has one.
This definition was taken right from GNU make manual, while Kbuild's
version is original.
Cc: Roman Zipp
On Tue, Jan 30, 2007 at 06:36:48PM -0800, Linus Torvalds wrote:
>
>
> On Tue, 30 Jan 2007, Mark Lord wrote:
> >
> > I believe our featherless leader said he though it was an ancient bug,
> > exasperated by something that went into 2.6.19.
> >
> > If Linus's opinion is correct (still?), then the
On Tuesday 30 January 2007 23:54, Maynard Johnson wrote:
> >>Why do you store them per spu in the first place? The physical spu
> >>doesn't have any relevance to this at all, the only data that is
> >>per spu is the sample data collected on a profiling interrupt,
> >>which you can then copy in the
On Jan 31, 2007, at 12:26 AM, Greg KH wrote:
On Tue, Jan 30, 2007 at 06:27:29PM -0800, Michael K. Edwards wrote:
On 1/29/07, Greg KH <[EMAIL PROTECTED]> wrote:
Free Linux Driver Development!
Yes, that's right, the Linux kernel community is offering all
companies
free Linux driver developm
On Tue, Jan 30, 2007 at 06:27:29PM -0800, Michael K. Edwards wrote:
> On 1/29/07, Greg KH <[EMAIL PROTECTED]> wrote:
> >Free Linux Driver Development!
> >
> >Yes, that's right, the Linux kernel community is offering all companies
> >free Linux driver development. ...
> [snip]
> >[1] for the CPUs t
On Tue, Jan 30, 2007 at 11:18:21PM -0600, Kumar Gala wrote:
>
> On Jan 30, 2007, at 11:11 PM, Andrew Morton wrote:
>
> >On Tue, 30 Jan 2007 22:55:38 -0600 (CST)
> >Kumar Gala <[EMAIL PROTECTED]> wrote:
> >
> >>Greg,
> >>
> >>There was some code added to warn if pci_get_subsys() is called
> >>an
On Wed, 31 Jan 2007, Nick Piggin wrote:
>
> I always thought that the AIO people didn't do this because they wanted
> to avoid context switch overhead.
I don't think that scheduling overhead was ever a really the reason, at
least not the primary one, and at least not on Linux. Sure, we can
pr
On Wednesday 31 January 2007 00:31, Carl Love wrote:
> Unfortunately, the only way we know how to
> figure out what the LFSR value that corresponds to the number in the
> sequence that is N before the last value (0xFF) is to calculate the
> previous value N times. It is like trying to ask what
On Tuesday 30 January 2007 22:41, Maynard Johnson wrote:
> Arnd Bergmann wrote:
> >>+ kt = ktime_set(0, profiling_interval);
> >>+ if (!spu_prof_running)
> >>+ goto STOP;
> >>+ hrtimer_forward(timer, timer->base->get_time(), kt);
> >>+ return HRTIMER_RESTART;
Nick Piggin wrote:
Linus Torvalds wrote:
On Wed, 31 Jan 2007, Benjamin Herrenschmidt wrote:
- We would now have some measure of task_struct concurrency. Read
that twice,
it's scary. As two fibrils execute and block in turn they'll each be
referencing current->. It means that we need to
On Tue, 30 Jan 2007, Kyle McMartin wrote:
> On Sat, Jan 27, 2007 at 07:28:07PM -0800, Zwane Mwaikambo wrote:
> > Hi Dave,
> > The following video card requires the agpgart driver ioctl
> > interface in order to detect video memory.
> >
>
> Tested with testgart.c on parisc64, seems to work a
On Tue, Jan 30, 2007 at 06:36:48PM -0800, Linus Torvalds wrote:
>
>
> On Tue, 30 Jan 2007, Mark Lord wrote:
> >
> > I believe our featherless leader said he though it was an ancient bug,
> > exasperated by something that went into 2.6.19.
> >
> > If Linus's opinion is correct (still?), then the
kbuild: improving option checking, Kbuild.include cleanup
GNU binutils, root users, tmpfiles, external modules ro builds must
be fixed to do the right thing now.
Cc: Roman Zippel <[EMAIL PROTECTED]>
Cc: Sam Ravnborg <[EMAIL PROTECTED]>
Cc: Horst Schirmeier <[EMAIL PROTECTED]>
Cc: Jan Beulich <[
Linus Torvalds wrote:
On Wed, 31 Jan 2007, Benjamin Herrenschmidt wrote:
- We would now have some measure of task_struct concurrency. Read that twice,
it's scary. As two fibrils execute and block in turn they'll each be
referencing current->. It means that we need to audit task_struct to m
On Jan 30, 2007, at 11:11 PM, Andrew Morton wrote:
On Tue, 30 Jan 2007 22:55:38 -0600 (CST)
Kumar Gala <[EMAIL PROTECTED]> wrote:
Greg,
There was some code added to warn if pci_get_subsys() is called
and the
pci_devices is empty.
I'm wondering if there is some point at which we know its
> NOTE! This is with the understanding that we *never* do any preemption.
> The whole point of the microthreading as far as I'm concerned is exactly
> that it is cooperative. It's not preemptive, and it's emphatically *not*
> concurrent (ie you'd never have two fibrils running at the same time
On Tue, 30 Jan 2007 22:55:38 -0600 (CST)
Kumar Gala <[EMAIL PROTECTED]> wrote:
> Greg,
>
> There was some code added to warn if pci_get_subsys() is called and the
> pci_devices is empty.
>
> I'm wondering if there is some point at which we know its ok for the
> pci_devices list be empty if the
Ric Wheeler wrote:
>
>
> Mark Lord wrote:
>
>> Eric D. Mudama wrote:
>>
>>>
>>> Actually, it's possibly worse, since each failure in libata will
>>> generate 3-4 retries. With existing ATA error recovery in the
>>> drives, that's about 3 seconds per retry on average, or 12 seconds
>>> per failu
Greg,
There was some code added to warn if pci_get_subsys() is called and the
pci_devices is empty.
I'm wondering if there is some point at which we know its ok for the
pci_devices list be empty if there are no devices on the bus so we can
stop printing the message.
On an embedded PPC refe
Siddha, Suresh B wrote:
Sorry for my delayed response. I was away on vacation.
What platform is this? what do you mean by crashing? Do you see a
system freeze or oops?
Its xeon-64 bit processor,running in 32-bit compatibility
mode(i386-code). We have not seen this problem in x86_64 envioronm
Hi,
Can you please suggest me from where do I get the VM
patches from kernel2.6.7 to kernel-2.6.19?
Thanks
Ram
__
Yahoo! India Answers: Share what you know. Learn something new
http://in.answers.yahoo.com/
-
To unsubscr
Yes, I know I said I would only do -rc6 and then the final 2.6.20, but the
thing is, the known regressions list didn't get whittled down as quickly
as I hoped, and as a result we now have a -rc7.
It's in good enough shape that I'd probably have been happy to just
release it as 2.6.20, but sinc
On Tue, 2007-01-30 at 22:20 -0500, Ric Wheeler wrote:
> Mark Lord wrote:
> > The number of retries is an entirely separate issue.
> > If we really care about it, then we should fix SD_MAX_RETRIES.
> >
> > The current value of 5 is *way* too high. It should be zero or one.
> >
> > Cheers
> >
> I th
Jeff Garzik wrote:
>> When we switch to PATA and drop old ide stack, what will happen ?
>> Will all driver be ported and full-feature, or some will be obsoleted ?
>
> All drivers for which we can find users will be ported. If any features
> disappear that's a bug.
>
Well, I have a long standin
I've included this as another user of the clocksource interface. I don't see a
usage for this across all achitectures. So a fully generic version isn't needed.
I modified this from the pre 2.6.20-rc6-mm2 release to make the routine smaller
and to make it select a clocksource inside the timer. It s
Drop.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
kernel/time/clocksource.c | 11 +--
1 file changed, 1 insertion(+), 10 deletions(-)
Index: linux-2.6.19/kernel/time/clocksource.c
===
--- linux-2.6.19.orig/kernel
Mark Lord wrote:
Eric D. Mudama wrote:
Actually, it's possibly worse, since each failure in libata will
generate 3-4 retries. With existing ATA error recovery in the
drives, that's about 3 seconds per retry on average, or 12 seconds
per failure. Multiply that by the number of blocks pa
The cifs entries in the dmesg log do not indicate any errors, much less
show the cause of this
particular problem.
The repeated entry:
CIFS VFS: Send error in SETFSUnixInfo = -5
is expected on connection to certain older versions of Samba servers (or
other servers that
only partially su
Drop.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
arch/i386/Kconfig |4 -
arch/i386/kernel/tsc.c | 49 +
include/linux/clocksource.h | 15 -
kernel/time/clocksource.c | 125 +---
kernel/timer.c
Drop.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
arch/i386/kernel/tsc.c | 51 +---
include/linux/clocksource.h | 11 ++---
kernel/timer.c |3 ++
3 files changed, 45 insertions(+), 20 deletions(-)
Index: linux-2.6.19
Normal systems often have almost everything registered in
device_initcall() . Most drivers are registered there, and usually if
people add code that needs an initcall they will either use
device_initcall() or module_init() which both result in the same
initcall..
When John created the clocksource
This moves the timekeeping sysfs override layer into timekeeping.c and
removes the get_next_clocksource and select_clocksource functions, and
their component variables, since they are no longer used.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
include/linux/clocksource.h |5 -
kern
This tree is mostly cleanups . I move timekeeping code into it's own
file, and I modify the clocksource interface to provide a more robust
API.
I've dropped some duplication off the hrt/dynamic tick patch set which
is all new to that tree and new to -mm. This is an -mm patch set , it's
not meant
From: Divy Le Ray <[EMAIL PROTECTED]>
Remove a status error string from the pci-x context
and add it where it belongs - the pci-e context.
Signed-off-by: Divy Le Ray <[EMAIL PROTECTED]>
---
drivers/net/cxgb3/t3_hw.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/dri
Drop.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
include/linux/clocksource.h |3 -
kernel/time/clocksource.c | 118 ++--
2 files changed, 61 insertions(+), 60 deletions(-)
Index: linux-2.6.19/include/linux/clocksource.h
==
From: Divy Le Ray <[EMAIL PROTECTED]>
Inform FW about the queue set->interface mapping.
Signed-off-by: Divy Le Ray <[EMAIL PROTECTED]>
---
drivers/net/cxgb3/adapter.h|2 +
drivers/net/cxgb3/cxgb3_main.c | 68 ++--
drivers/net/cxgb3/sge.c|
From: Divy Le Ray <[EMAIL PROTECTED]>
Clean up FW version checking.
The supported FW version is now 3.1.
Signed-off-by: Divy Le Ray <[EMAIL PROTECTED]>
---
drivers/net/cxgb3/cxgb3_main.c | 15 ---
drivers/net/cxgb3/firmware_exports.h | 27 +++
drive
From: Divy Le Ray <[EMAIL PROTECTED]>
Use tabs in comments.
Signed-off-by: Divy Le Ray <[EMAIL PROTECTED]>
---
drivers/net/cxgb3/t3_hw.c | 30 +++---
1 files changed, 15 insertions(+), 15 deletions(-)
diff --git a/drivers/net/cxgb3/t3_hw.c b/drivers/net/cxgb3/t3_hw.c
From: Divy Le Ray <[EMAIL PROTECTED]>
Include in adapter.h
Signed-off-by: Divy Le Ray <[EMAIL PROTECTED]>
---
drivers/net/cxgb3/adapter.h |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/net/cxgb3/adapter.h b/drivers/net/cxgb3/adapter.h
index 8902007..97e35c8 10
From: Divy Le Ray <[EMAIL PROTECTED]>
Offload packets may be DMAed long after their SGE Tx descriptors are done
so they must remain mapped until they are freed rather than until their
descriptors are freed. Unmap such packets through an skb destructor.
Signed-off-by: Divy Le Ray <[EMAIL PROTECTE
From: Divy Le Ray <[EMAIL PROTECTED]>
Dual licensing, needed for OFED 1.2
Signed-off-by: Divy Le Ray <[EMAIL PROTECTED]>
---
drivers/net/cxgb3/adapter.h | 33 +++
drivers/net/cxgb3/ael1002.c | 34 +++-
drivers/net/cxgb3/common.h
From: Divy Le Ray <[EMAIL PROTECTED]>
In some cases, SG_DATA_INTR won't clear on read and the following
interrupt may cause us to assert because NAPI is already scheduled.
Remove the assertion, NAPI can handle attempts to rearm it while
it's already scheduled.
Signed-off-by: Divy Le Ray <[EMAIL
From: Divy Le Ray <[EMAIL PROTECTED]>
Remove tx credit coalescing done in SW.
The HW is caring care of it already.
Signed-off-by: Divy Le Ray <[EMAIL PROTECTED]>
---
drivers/net/cxgb3/sge.c | 75 +--
1 files changed, 14 insertions(+), 61 deletions(-
From: Divy Le Ray <[EMAIL PROTECTED]>
Clean up the tp_config() routine.
Signed-off-by: Divy Le Ray <[EMAIL PROTECTED]>
---
drivers/net/cxgb3/t3_hw.c | 16 +---
1 files changed, 5 insertions(+), 11 deletions(-)
diff --git a/drivers/net/cxgb3/t3_hw.c b/drivers/net/cxgb3/t3_hw.c
ind
Jeff,
I'm sending a series of incremental patches updating
the cxgb3 driver. These patches are built against
netdev#upstream.
Cheers,
Divy
-
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.k
Modifies the way clocks are switched to in the timekeeping code. The original
code would constantly monitor the clocksource list checking for newly added
clocksources. I modified this by using atomic types to signal when a new clock
is added. This allows the operation to be used only when it's need
Update avr32 for new flags.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
arch/avr32/kernel/time.c |1 -
1 file changed, 1 deletion(-)
Index: linux-2.6.19/arch/avr32/kernel/time.c
===
--- linux-2.6.19.orig/arch/avr32/ker
Hope you will be resubmitting this.
> +/*
> + * rfkill key structure.
> + */
> +struct rfkill_key {
> + /*
> + * For sysfs representation.
> + */
> + struct class_device *cdev;
> +
> + /*
> + * Pointer to rfkill structure
> + * that was filled in by key driver.
> +
Adds a call back interface for register/rating change events. This is also used
later in this series to signal other interesting events.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
include/linux/clocksource.h | 37 +
include/linux/timekeeping.h |
Update ARM for new flags.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
arch/arm/mach-imx/time.c |1 -
arch/arm/mach-ixp4xx/common.c |1 -
arch/arm/mach-netx/time.c |1 -
arch/arm/mach-pxa/time.c |1 -
4 files changed, 4 deletions(-)
Index: linux-2.6.19/arch
This patch modifies the current clocksource API so that clocks
can be masked if they have specific negative qualities. For
instance, if a clock is not atomic you can choose not to include
it in the list you select from, atomic in this case being lockless.
The following qualities can be masked o
Compile patch .. This just adds some code so the next few patches will compile.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
include/linux/clocksource.h |6 ++
1 file changed, 6 insertions(+)
Index: linux-2.6.19/include/linux/clocksource.h
===
Update x86_64 for new flags.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
arch/x86_64/kernel/hpet.c |1 -
arch/x86_64/kernel/tsc.c | 11 ---
2 files changed, 4 insertions(+), 8 deletions(-)
Index: linux-2.6.19/arch/x86_64/kernel/hpet.c
Uses the block notifier to replace the functionality of update_callback().
update_callback() was a special case specifically for the tsc, but including
it in the clocksource structure duplicated it needlessly for other clocks.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
arch/i386/kernel
One new API call clocksource_get_clock() which allows clocks to be selected
based on their name, or if the name is null the highest rated clock is returned.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
include/linux/clocksource.h | 12
kernel/time/clocksource.c | 18 ++
Move the generic timekeeping code from kernel/timer.c to
kernel/time/timekeeping.c . This requires some glue code which is
added to the include/linux/timekeeping.h header.
I tried to be as careful as possible in picking up recent changes to
the timekeeping code. This patches is on top of -mm , and
Update i386 for new flags.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
arch/i386/kernel/hpet.c|1 -
arch/i386/kernel/i8253.c |1 +
arch/i386/kernel/tsc.c | 23 +++
arch/i386/kernel/vmitime.c |2 +-
4 files changed, 13 insertions(+), 14 deletio
Drop.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
arch/x86_64/kernel/tsc.c | 31 +--
1 file changed, 21 insertions(+), 10 deletions(-)
Index: linux-2.6.19/arch/x86_64/kernel/tsc.c
===
--- linu
This is something Thomas already dropped, and I'm just sticking
with that .. If you register your clocksource _twice_ your kernel will
likely not work correctly (and might crash).
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
kernel/time/clocksource.c | 19 ++-
1 file ch
Update drivers/ for new flags.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
drivers/clocksource/acpi_pm.c|2 +-
drivers/clocksource/cyclone.c|1 -
drivers/clocksource/scx200_hrt.c |1 -
3 files changed, 1 insertion(+), 3 deletions(-)
Index: linux-2.6.19/drivers/clock
Update mips for new flags.
Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
---
arch/mips/kernel/time.c |1 -
1 file changed, 1 deletion(-)
Index: linux-2.6.19/arch/mips/kernel/time.c
===
--- linux-2.6.19.orig/arch/mips/kernel/
Converts the original plain list into a sorted list based on the clock rating.
Later in my tree this allows some of the variables to be dropped since the
highest rated clock is always at the front of the list. This also does some
other nice things like allow the sysfs files to print the clocks in a
On Tue, Jan 30, 2007 at 05:11:32PM -0800, Andrew Morton wrote:
> On Wed, 31 Jan 2007 11:44:36 +1100
> David Chinner <[EMAIL PROTECTED]> wrote:
>
> > On Mon, Jan 29, 2007 at 06:15:57PM -0800, Andrew Morton wrote:
> > > We still don't know what is the source of kmap() activity which
> > > necessitat
On Sat, Jan 27, 2007 at 07:28:07PM -0800, Zwane Mwaikambo wrote:
> Hi Dave,
> The following video card requires the agpgart driver ioctl
> interface in order to detect video memory.
>
Tested with testgart.c on parisc64, seems to work alright. Thanks for
doing this work, Zwane. I've been me
On Tue, 30 Jan 2007, Linus Torvalds wrote:
>
> Does that mean that we might not have some cases where we'd need to make
> sure we do things differently? Of course not. Something migt show up. But
> this actually makes it very clear what the difference between "struct
> thread_struct" and "str
scripts: replace gawk, head, bc with shell, update
Replacing overhead of using some (external) programs
instead of good old `sh'.
Cc: Roman Zippel <[EMAIL PROTECTED]>
Cc: Sam Ravnborg <[EMAIL PROTECTED]>
Cc: William Stearns <[EMAIL PROTECTED]>
Cc: Martin Schlemmer <[EMAIL PROTECTED]>
Signed-o
On Wed, 31 Jan 2007, Benjamin Herrenschmidt wrote:
> > - We would now have some measure of task_struct concurrency. Read that
> > twice,
> > it's scary. As two fibrils execute and block in turn they'll each be
> > referencing current->. It means that we need to audit task_struct to make
> >
On Tue, 30 Jan 2007, Mark Lord wrote:
>
> I believe our featherless leader said he though it was an ancient bug,
> exasperated by something that went into 2.6.19.
>
> If Linus's opinion is correct (still?), then the bug exists in all
> kernels since somewhere back in the 2.4.xx days.
The issue
On Tue, 30 Jan 2007 13:25:58 +0100
Jean Delvare <[EMAIL PROTECTED]> wrote:
> So here comes the third
> (and hopefully last) iteration of the patch:
argh, it looks like I sent v2 to Linus.
Here's the missing bit. Please confirm that we want it?
From: Jean Delvare <[EMAIL PROTECTED]>
Add speci
Jouni Malinen wrote:
> On Tue, Jan 30, 2007 at 01:08:29AM -0600, Larry Finger wrote:
>
>> Any AP with a hidden SSID will only respond to probe requests that specify
>> its SSID, and will ignore
>> any other probes. In addition, the response will have an empty SSID field.
>> These responses are t
On 1/29/07, Greg KH <[EMAIL PROTECTED]> wrote:
Free Linux Driver Development!
Yes, that's right, the Linux kernel community is offering all companies
free Linux driver development. ...
[snip]
[1] for the CPUs that support the bus types that your device works on.
Bravo! Now, is there a mess
On Tue, Jan 30, 2007 at 06:07:14PM -0500, Phillip Susi wrote:
> It most certainly matters where the error happened because "you are
> screwd" is not an acceptable outcome in a mission critical application.
An I/O error is not an acceptable outcome in a mission critical app,
all mission critical
Matt Domsch wrote:
As one who regularly fills a sponsor slot (though I have also gotten
an invitation on merit in the past), I don't believe the sponsor slot
people detract from the sessions. Most of the time we keep quiet,
occasionally offering our insights or challenges. Jonathan's writeups
a
On Sun, Jan 28, 2007 at 06:48:26PM -0500, Mike Frysinger wrote:
> the statfs header exports some structs to userspace ... the parisc statfs64
> struct currently uses u64 so the trivial attached patch fixes it to use __u64
> -mike
ack'd and merged. can you please not attach patches but properly se
On Tue, Jan 30, 2007 at 05:24:28PM -0800, Greg KH wrote:
> On Wed, Jan 31, 2007 at 02:13:40AM +0100, Adrian Bunk wrote:
> > On Tue, Jan 30, 2007 at 11:10:20AM -0800, Greg KH wrote:
> > > On Tue, Jan 30, 2007 at 09:45:50AM -0800, Roland Dreier wrote:
> > >...
> > > > And there are plenty of document
On Wed, Jan 31, 2007 at 11:19:15AM +1000, Trent Waddington wrote:
> On 1/31/07, Adrian Bunk <[EMAIL PROTECTED]> wrote:
> >Would someone from your long list of people e.g. be willing to maintain
> >drivers/block/floppy.c ?
>
> I have a floppy drive! Will have to go buy some disks though. What's
>
On 1/31/07, Greg KH <[EMAIL PROTECTED]> wrote:
On Wed, Jan 31, 2007 at 02:13:40AM +0100, Adrian Bunk wrote:
> On Tue, Jan 30, 2007 at 11:10:20AM -0800, Greg KH wrote:
> > On Tue, Jan 30, 2007 at 09:45:50AM -0800, Roland Dreier wrote:
> >...
> > > And there are plenty of documented devices that no
On Tue, 2007-01-30 at 15:45 -0800, Zach Brown wrote:
> > Btw, I noticed that you didn't Cc Ingo. Definitely worth doing. Not
> > just
> > because he's basically the normal scheduler maintainer, but also
> > because
> > he's historically been involved in things like the async filename
> > look
> - We would now have some measure of task_struct concurrency. Read that twice,
> it's scary. As two fibrils execute and block in turn they'll each be
> referencing current->. It means that we need to audit task_struct to make
> sure
> that paths can handle racing as its scheduled away. The cu
Linus Torvalds wrote:
>
> On Tue, 30 Jan 2007, Jeff Layton wrote:
>> Also, that patch would break many 32-bit programs not compiled with large
>> offsets when run in compatibility mode on a 64-bit kernel. If they were to
>> do a stat on this inode, it would likely generate an EOVERFLOW error since
On Wed, 31 Jan 2007 00:52:15 +0100
Adrian Bunk <[EMAIL PROTECTED]> wrote:
> On Mon, Jan 29, 2007 at 04:04:48PM -0500, Mike Houston wrote:
> > I've been using Adrian's 2.6.16 kernel releases on two internet
> > servers that I look after remotely. One of them is RHEL 4 the
> > other is Fedora Core
On Tue, 30 Jan 2007 15:31:09 -0800
Carl Love <[EMAIL PROTECTED]> wrote:
> An LFSR sequence is similar to a pseudo random number sequence. For a 24
> bit LFSR sequence each number between 0 and 2^24 will occur once in the
> sequence but not in a normal counting order. The hardware uses the LFSR
>
Eric D. Mudama wrote:
Actually, it's possibly worse, since each failure in libata will
generate 3-4 retries. With existing ATA error recovery in the drives,
that's about 3 seconds per retry on average, or 12 seconds per failure.
Multiply that by the number of blocks past the error to comple
Jeff Layton wrote:
Bodo Eggert wrote:
> change pipefs to use a unique inode number equal to the memory
> address unless it would be truncated.
>
> Signed-Off-By: Bodo Eggert <[EMAIL PROTECTED]>
> ---
> Tested on i386.
>
> --- 2.6.19/fs/pipe.c.ori2007-01-30 22:02:46.0 +0100
>
James Bottomley wrote:
First off, please send SCSI patches to the SCSI list:
Fixed already, thanks!
This patch fixes the behaviour to be similar to what we had originally.
When a bad sector is encounted, SCSI will now work around it again,
failing *only* the bad sector itself.
Erm, but th
Adrian Bunk wrote:
On Tue, Jan 30, 2007 at 09:13:00AM +1100, Bron Gondwana wrote:
We do a lot of Cyrus which does a lot of MMAP - and we also use the
Areca driver - which are both strong reasons to move to 2.6.19.2, but
if the MMAP fix was ported back to 2.6.16 we might consider staying
there i
On Tue, Jan 30, 2007 at 03:21:19PM -0800, Andrew Morton wrote:
> On Tue, 30 Jan 2007 12:55:58 -0800
> Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> > y'know, four or five years back I fixed this bug by doing
> >
> > current->locked_page = page;
> >
> > in the write() code, and then teaching t
On Tue, Jan 30, 2007 at 05:07:57PM -0800, Roland Dreier wrote:
> > > To me, it's clear that historically the community hasn't delivered on
> >
> > How is that clear? As noted in the specific examples I provided, that
> > is how a large number of popular drivers and subsystems have been
> > d
On Tue, 30 Jan 2007, Jeff Layton wrote:
>
> Also, that patch would break many 32-bit programs not compiled with large
> offsets when run in compatibility mode on a 64-bit kernel. If they were to
> do a stat on this inode, it would likely generate an EOVERFLOW error since
> the pointer address wo
On Wed, 31 Jan 2007 02:16:43 +0100
Tilman Schmidt <[EMAIL PROTECTED]> wrote:
> Am 30.01.2007 23:18 schrieb Maciej Rutecki:
> > Second problem, power button doesn't work. When I pressed it, I has this
> > error:
> >
> > ACPI Error (evevent-0305): No installed handler for fixed event
> > [0002]
On Wed, Jan 31, 2007 at 02:13:40AM +0100, Adrian Bunk wrote:
> On Tue, Jan 30, 2007 at 11:10:20AM -0800, Greg KH wrote:
> > On Tue, Jan 30, 2007 at 09:45:50AM -0800, Roland Dreier wrote:
> >...
> > > And there are plenty of documented devices that no one cares enough
> > > about to submit a driver
Robert P. J. Day wrote:
On Tue, 30 Jan 2007, Nick Piggin wrote:
Robert P. J. Day wrote:
Add the inline function "is_power_of_2()" to log2.h, where the value
zero is *not* considered to be a power of two.
Signed-off-by: Robert P. J. Day <[EMAIL PROTECTED]>
/*
+ * Determine whether some
Memorystick support is not yet implemented (work in progress).
--- [EMAIL PROTECTED] wrote:
> Running recent kernels the insertion of a MemoryStick into the card
> reader of a Sony Vaio VGNSZ3XWP is detected but the card does not seem
> to be probed for partitions and hence is not made available
On Tuesday 30 January 2007 12:35, Joe Harvell wrote:
> I am trying to enable all the power saving features I can on my Conroe
> E6600. After much searching on the web, I am a little confused about
> the Linux kernel support for ACPI on the Conroe.
>
> Here is my setup:
> Intel Core2 Duo E6600
> A
Bodo Eggert wrote:
> change pipefs to use a unique inode number equal to the memory
> address unless it would be truncated.
>
> Signed-Off-By: Bodo Eggert <[EMAIL PROTECTED]>
> ---
> Tested on i386.
>
> --- 2.6.19/fs/pipe.c.ori 2007-01-30 22:02:46.0 +0100
> +++ 2.6.19/fs/pipe.c 200
1 - 100 of 486 matches
Mail list logo
