[cc'ing Ric, Hannes and Dongjun, Hello. Feel free to drag other people in.]
Robert Hancock wrote:
Jens Axboe wrote:
But we can't really change that, since you need the cache flushed before
issuing the FUA write. I've been advocating for an ordered bit for
years, so that we could just do:
On Wed, Feb 21 2007, Tejun Heo wrote:
[cc'ing Ric, Hannes and Dongjun, Hello. Feel free to drag other people in.]
Robert Hancock wrote:
Jens Axboe wrote:
But we can't really change that, since you need the cache flushed before
issuing the FUA write. I've been advocating for an ordered
On Mon, Feb 19 2007, Robert Hancock wrote:
Jens Axboe wrote:
But we can't really change that, since you need the cache flushed before
issuing the FUA write. I've been advocating for an ordered bit for
years, so that we could just do:
3. w/FUA+ORDERED
normal operation - barrier issued -
Jens Axboe wrote:
On Wed, Feb 21 2007, Tejun Heo wrote:
[cc'ing Ric, Hannes and Dongjun, Hello. Feel free to drag other people in.]
Robert Hancock wrote:
Jens Axboe wrote:
But we can't really change that, since you need the cache flushed before
issuing the FUA write. I've been advocating
On Wed, Feb 21 2007, Tejun Heo wrote:
Jens Axboe wrote:
On Wed, Feb 21 2007, Tejun Heo wrote:
[cc'ing Ric, Hannes and Dongjun, Hello. Feel free to drag other people
in.]
Robert Hancock wrote:
Jens Axboe wrote:
But we can't really change that, since you need the cache flushed
On Sat, Feb 17, 2007 at 09:51:46PM -0800, Andrew Morton wrote:
...
Changes since 2.6.20-mm1:
...
git-ubi.patch
...
git trees
...
If you select an option, you have to ensure that the dependencies of all
options you are select'ing are fulfilled.
This patch fixes the following compile error:
Marc Perkel wrote (ao):
I have a partition that used to be part of a software
raid 1 array. It is now loaded as /dev/sda3 but I'd
like to mirror it to /dev/sdb3 without losing the data
on the drive. I'm a little nervous about how to set it
up as I don't want to wipe out the data.
How do I
From: Pekka Enberg [EMAIL PROTECTED]
As suggested by Arjan, make GCC warn about classic misuse of the realloc API.
Cc: Arjan van de Ven [EMAIL PROTECTED]
Signed-off-by: Pekka Enberg [EMAIL PROTECTED]
---
include/linux/slab.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index:
From: Arjan van de Ven [EMAIL PROTECTED]
Subject: Use symbolic constants in inline assembly
This patch replaces several of the %0/%1 uses in x86-64 inline assembly
with symbolic names (this is a new gcc 3.x feature, but that's ok now).
This tends to, imo, make the inline assembly a lot more
NB: I'm not subscribed so please CC me in any reply! Thanks...
Hi there,
Just attempted a build of vanilla 2.6.20-rc1 and got a failure with our
usual defconfig. Notably, we build IPV6 support as modular - this seems to
be the source of the problem.
If any other info is required, please
On Wednesday February 21, [EMAIL PROTECTED] wrote:
Greetings,
I just got a unusual message from lockd on a webserver running a
custom compiled 2.6.13.4 (yes it is ancient, I know).
# uname -a
Linux webserv.somedomain.example 2.6.13.4 #1 SMP Wed Nov 16 10:03:05
CET 2005 i686 unknown
#
Kawai, Hidehiro [EMAIL PROTECTED] wrote:
Is coredump_setting_sem a global semaphore? If so, it prevents concurrent
core dumping.
No, it doesn't. Look again:
int do_coredump(long signr, int exit_code, struct pt_regs * regs)
{
setup vars
Kay Sievers wrote:
On 2/13/07, Kay Sievers [EMAIL PROTECTED] wrote:
On Tue, 2007-02-13 at 17:04 +0100, Marcel Holtmann wrote:
kernel BUG at lib/iomap.c:254!
invalid opcode: [#1]
...
The screen picture is here:
http://vrfy.org/pci_iounmap.jpg
It's a Thinkpad T43p.
Chris Snook [EMAIL PROTECTED] wrote:
Patch 1 fixes the case statements to use the symbolic constants in
include/linux/fs.h, and should not be at all controversial.
Patch 2 adds a SEEK_MAX and uses it to validate user arguments. This makes
the code a little cleaner and also enables future
On 21/02/07, Neil Brown [EMAIL PROTECTED] wrote:
On Wednesday February 21, [EMAIL PROTECTED] wrote:
Greetings,
I just got a unusual message from lockd on a webserver running a
custom compiled 2.6.13.4 (yes it is ancient, I know).
# uname -a
Linux webserv.somedomain.example 2.6.13.4 #1 SMP
On Wed, Feb 21, 2007 at 11:33:31AM +, David Howells wrote:
Kawai, Hidehiro [EMAIL PROTECTED] wrote:
Is coredump_setting_sem a global semaphore? If so, it prevents concurrent
core dumping.
No, it doesn't. Look again:
int do_coredump(long signr, int exit_code, struct pt_regs
Does it work if you give 'irqpoll' kernel parameter?
--
tejun
-
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/
21 Şub 2007 Çar tarihinde, Greg KH şunları yazmıştı:
Responses should be made by Friday February 23 00:00 UTC. Anything
received after that time might be too late.
We have still some CVEish patches in our package which maybe you want to
consider adding into -stable.
*
On Wednesday 21 February 2007 12:10, Arjan van de Ven wrote:
From: Arjan van de Ven [EMAIL PROTECTED]
Subject: Use symbolic constants in inline assembly
This patch replaces several of the %0/%1 uses in x86-64 inline assembly
with symbolic names (this is a new gcc 3.x feature, but that's ok
This patch works around a warning with -Wmissing-prototypes in
arch/i386/kernel/asm-offsets.c
The warning isn't gcc's fault - asm-offsets.c is simply a special file.
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
---
--- linux-2.6.20-mm2/arch/i386/kernel/asm-offsets.c.old 2007-02-20
On Sat, Feb 17, 2007 at 09:51:46PM -0800, Andrew Morton wrote:
...
Changes since 2.6.20-mm1:
...
+i386-irq-kill-irq-compression.patch
...
x86 updates
...
This patch removes a no longer used variable.
Spotted by the GNU C compiler.
Signed-off-by: Adrian Bunk [EMAIL PROTECTED]
---
---
On Tue, Jan 23, 2007 at 09:10:08PM -0200, Mauro Carvalho Chehab wrote:
Em Ter, 2007-01-23 às 20:57 +0300, Oleg Nesterov escreveu:
I am pretty sure the bug is real, but the patch may be wrong, please review.
We are doing -buf_prepare(buf) before adding buf to q-stream list. This
means
On Mon, Feb 19, 2007 at 06:56:20PM -0800, H. Peter Anvin wrote:
It's not a precondition for a file descriptor, either. There are plenty
of ioctl-only device drivers in existence.
Furthermore, a file descriptor doesn't imply a device entry. Consider
pipe(2), for example.
As far as the
Michal Piotrowski napisał(a):
On 17/02/07, Alex Riesen [EMAIL PROTECTED] wrote:
Thomas Gleixner, Sat, Feb 17, 2007 16:14:17 +0100:
On Sat, 2007-02-17 at 15:47 +0100, Alex Riesen wrote:
164 if (need_resched())
165 goto end;
166
167
From: Pekka Enberg [EMAIL PROTECTED]
We must not overwrite the same pointer that is passed to krealloc()
because it can return NULL without freeing the buffer. Fixes a memory
leak introduced by me.
Cc: Josef Sipek [EMAIL PROTECTED]
Signed-off-by: Pekka Enberg [EMAIL PROTECTED]
---
Udo van den Heuvel [EMAIL PROTECTED] writes:
So if my non-VIA riser card can use DN 19 and also INT_A things should work?
That INT_A may be INT_A from their (motherboard) point of view, but
the riser card doesn't know about that, it only knows INTs as seen
at its PCI edge connector (so this
On Wed, 21 February 2007 05:36:22 +0100, Juan Piernas Canovas wrote:
I don't see how you can guarantee 50% free segments. Can you explain
that bit?
It is quite simple. If 50% of your segments are busy, and the other 50%
are free, and the file system needs a new segment, the cleaner starts
On Wednesday 21 February 2007 00:41, [EMAIL PROTECTED] wrote:
This is a note to let you know that we have just queued up the patch titled
Subject: x86_64: fix 2.6.18 regression - PTRACE_OLDSETOPTIONS should
be accepted
to the 2.6.18-stable tree. Its filename is
Since you are still
Jan-Benedict Glaw wrote:
On Tue, 2007-02-20 15:36:56 +0100, Helge Hafting [EMAIL PROTECTED] wrote:
If you have a need for secret source code, stuff most of it
in userspace. Make the drivers truly minimal; perhaps their
open/closed status won't matter that much when the bulk
of the code and
These functions were inlines before 8b9365d753d9870bb6451504c13570b81923228f.
Now EXPORT_SYMBOL() them to allow them to be used in modules again.
Signed-off-by: Rolf Eike Beer [EMAIL PROTECTED]
---
commit 0a543599f4a9ea02b587bda26e0e11ae94774f61
tree aa815eab413d2575925b0964a1fa01d41439b26b
These functions were inlines before 8b9365d753d9870bb6451504c13570b81923228f.
Now EXPORT_SYMBOL() them to allow them to be used in modules again.
Signed-off-by: Rolf Eike Beer [EMAIL PROTECTED]
---
Sent once again, this time without PGP signature so importing into git is
easier.
commit
Hi,
21 Şub 2007 Çar 06:53 tarihinde, Linus Torvalds şunları yazmıştı:
Ok, the merge window for 2.6.21 has closed, and -rc1 is out there.
CHK include/linux/version.h
CHK include/linux/utsrelease.h
CHK include/linux/compile.h
CC [M] drivers/char/ip2/ip2main.o
In file
On Tue, 2007-02-20 at 20:53 -0800, Linus Torvalds wrote:
But there's a ton of architecture updates (arm, mips, powerpc, x86, you
name it), ACPI updates, and lots of driver work. And just a lot of
cleanups.
Have fun,
Yup. Fun starts in drivers/net/e1000
e1000 is not working anymore. ifup
On Wed, 2007-02-21 at 14:12 +0100, Rolf Eike Beer wrote:
These functions were inlines before 8b9365d753d9870bb6451504c13570b81923228f.
Now EXPORT_SYMBOL() them to allow them to be used in modules again.
please do not add random exports without users; exports eat up kernel
size and memory. At
If the badness of a process is zero then oom_adj0 has no effect. This
patch makes sure that the oom_adj shift actually increases badness
points appropriately.
I am not subscribed. Please CC me with any comments. Thanks.
Signed-off-by: Joshua N. Pritikin [EMAIL PROTECTED]
---
Greg KH wrote:
This is the start of the stable review cycle for the 2.6.19.5 release.
This will probably be the last release of the 2.6.19-stable series, so
if there are patches that you feel should be applied to that tree,
please let me know.
There is one here: Missing critical
I wrote:
I hope you can extract the patch from this MIME attachment.
Probably not unless I attach it for real.
--
Stefan Richter
-=-=-=== --=- =-=-=
http://arcgraph.de/sr/
Subject: [PATCH] Missing critical phys_to_virt in lib/swiotlb.c
From: David Moore [EMAIL PROTECTED]
Date: Sun, 04 Feb
s390 machines (z900 or higher) provide hardware support for creating Linux
dumps on SCSI disks. Our current implementation consists of a userspace
application running on an special Linux dump kernel, which exploits the
s390 hardware support. Since both parts (kernel and userspace) belong
together,
Kernel part of the s390 SCSI dumper: zcore character device driver.
Acked-by: Martin Schwidefsky [EMAIL PROTECTED]
Signed-off-by: Michael Holzheu [EMAIL PROTECTED]
---
Documentation/s390/zfcpdump.txt | 41 +
arch/s390/Kconfig |7
arch/s390/kernel/early.c|3
Userspace part of the s390 SCSI dumper.
Acked-by: Martin Schwidefsky [EMAIL PROTECTED]
Signed-off-by: Michael Holzheu [EMAIL PROTECTED]
---
arch/s390/Makefile|4
arch/s390/zfcpdump/Makefile |5
arch/s390/zfcpdump/defconfig.zfcpdump | 467
Hi,
I've an ASUS A8V motherboard with a via chipset:
[EMAIL PROTECTED] % lspci
00:00.0 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:00.1 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:00.2 Host bridge: VIA Technologies, Inc. K8T800Pro Host Bridge
00:00.3 Host
From: David Howells [EMAIL PROTECTED]
Add support for direct mapping through mtdconcat, if possible, by attaching the
samebacking_dev_info structure to the master.
It has some restrictions:
(1) It won't permit direct mapping of concatenated devices that have differing
BDIs.
(2) It
From: David Howells [EMAIL PROTECTED]
Present backing device capabilities for MTD character device files to allow
NOMMU mmap to do direct mapping where possible.
Signed-Off-By: David Howells [EMAIL PROTECTED]
---
drivers/mtd/Makefile |2 +
drivers/mtd/chips/map_ram.c | 17
From: David Howells [EMAIL PROTECTED]
Change RomFS so that it can use MTD devices directly - without the intercession
of the block layer - as well as using block devices.
This permits RomFS:
(1) to use the MTD direct mapping facility available under NOMMU conditions if
the underlying
From: David Howells [EMAIL PROTECTED]
Generalise the handling of MTD-specific superblocks so that JFFS2 and ROMFS can
both share it.
Signed-Off-By: David Howells [EMAIL PROTECTED]
---
drivers/mtd/Makefile |2
drivers/mtd/mtdsuper.c| 231
Where is largefile issue in ecryptfs.
Even if we want open file on ia32 with explicit O_LARGEFILE, lower_file will
be opened without O_LARGEFILE flag this result in various errors in dmesg
and data corruption.
Testcase:
write 'a' chars beyond 2Gb
# strace ./writer_test root/file
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
On Wed, Feb 21, 2007 at 01:07:22PM +0300, Dmitriy Monakhov wrote:
Where is largefile issue in ecryptfs.
Thanks for your thorough work on resolving such issues. We will
integrate your patches and testcases into the next release as soon as
we get
On Sat, Feb 17, 2007 at 06:35:31PM -0800, Roland McGrath wrote:
Looking at mainline x86_64 ptrace code I think hole for u_debugreg[4]
and [5] is also needed.
It's not. The utrace_regset for the debugregs already has that behavior
for those two words, so mapping all 8 uarea words to the
Michael Halcrow [EMAIL PROTECTED] writes:
On Wed, Feb 21, 2007 at 01:07:22PM +0300, Dmitriy Monakhov wrote:
Where is largefile issue in ecryptfs.
Thanks for your thorough work on resolving such issues. We will
integrate your patches and testcases into the next release as soon as
we get a
On Mon, Feb 19, 2007 at 01:38:35PM -0800, Zach Brown wrote:
aio: propogate post-EIOCBQUEUED errors to completion event
This addresses an oops reported by Leonid Ananiev [EMAIL PROTECTED]
as archived at http://lkml.org/lkml/2007/2/8/337.
O_DIRECT kicks off bios and returns -EIOCBQUEUED to
New devolpments.
I have upgraded to 2.6.16.41, applied a patch sent by Frederik that
removed the changed made in http://lkml.org/lkml/2005/6/23/266 and
activated some more kernel debug, i.e., CONFIG_KALLSYMS_ALL,
CONFIG_DEBUG_KERNEL, CONFIG_DETECT_SOFTLOCKUP, CONFIG_DEBUG_SLAB,
Arjan van de Ven wrote:
On Wed, 2007-02-21 at 14:12 +0100, Rolf Eike Beer wrote:
These functions were inlines before
8b9365d753d9870bb6451504c13570b81923228f. Now EXPORT_SYMBOL() them to
allow them to be used in modules again.
please do not add random exports without users; exports eat up
On 02/21, Srivatsa Vaddagiri wrote:
On Tue, Feb 20, 2007 at 11:09:36PM +0300, Oleg Nesterov wrote:
Which caller are you referring to here? Maybe we can decide on the
option after we see the users of flush_workqueue() in DOWN_PREPARE.
mm/slab.c:cpuup_callback()
The
Does this fix the oops ?
Alan
diff -u --new-file --recursive --exclude-from /usr/src/exclude
linux.vanilla-2.6.20-mm2/drivers/ata/pata_pcmcia.c
linux-2.6.20-mm2/drivers/ata/pata_pcmcia.c
--- linux.vanilla-2.6.20-mm2/drivers/ata/pata_pcmcia.c 2007-02-20
13:37:58.0 +
+++
On Wed, Feb 21, 2007 at 05:30:10PM +0300, Oleg Nesterov wrote:
On 02/21, Srivatsa Vaddagiri wrote:
On Tue, Feb 20, 2007 at 11:09:36PM +0300, Oleg Nesterov wrote:
Which caller are you referring to here? Maybe we can decide on the
option after we see the users of flush_workqueue() in
Revised DRAC4 warning as Jeff suggested, this one includes more info
about why the problem occurs
Signed-off-by: Alan Cox [EMAIL PROTECTED]
diff -u --new-file --recursive --exclude-from /usr/src/exclude
linux.vanilla-2.6.20-mm2/drivers/ide/pci/siimage.c
Backlight control support for the PXA fram buffer.
Signed-off-by: Rodolfo Giometti [EMAIL PROTECTED]
---
Each platform should define the backlight properties in its own setup
file in linux/arch/arm/mach-pxa/ as follow:
static int pxafb_bl_get_brightness(struct backlight_device *bl_dev)
{
Rafael,
On Sat, Feb 17, 2007 at 12:24:45PM +0100, Rafael J. Wysocki wrote:
Pavel, do you think we can remove the PF_NOFREEZE from bluetooth, BTW?
The create_workqueue by default marks the worker_threads to be
non_freezable. For cpu hotplug, all workqueues can be frozen
except the kthread
Jose Goncalves wrote:
New devolpments.
I have upgraded to 2.6.16.41, applied a patch sent by Frederik that
removed the changed made in http://lkml.org/lkml/2005/6/23/266 and
activated some more kernel debug, i.e., CONFIG_KALLSYMS_ALL,
CONFIG_DEBUG_KERNEL, CONFIG_DETECT_SOFTLOCKUP,
On Tue, 20 February 2007 17:46:13 -0800, Vijay Sampath wrote:
The files cfi_cmdset_0002.c and cfi_cmdset_0020.c do not initialize
their wait queues like is done in cfi_cmdset_0001.c. This causes an
oops when the wait queue is accessed. I have copied the code from
cfi_cmdset_0001.c that is
Apologies for brain failure, below should read 2.6.21-rc1.
Everything else should be correct.
Michael-Luke Jones
On 21 Feb 2007, at 10:50, M.L. Jones wrote:
NB: I'm not subscribed so please CC me in any reply! Thanks...
Hi there,
Just attempted a build of vanilla 2.6.20-rc1 and got a
Krzysztof Halasa wrote:
Udo van den Heuvel [EMAIL PROTECTED] writes:
So if my non-VIA riser card can use DN 19 and also INT_A things should work?
That INT_A may be INT_A from their (motherboard) point of view, but
the riser card doesn't know about that, it only knows INTs as seen
at its
I tried to check cat operations for tiny_tty driver from LDD book.
What is wrong with cat operation here?
Here is the output from strace cat hello /dev/my_tty1
[EMAIL PROTECTED]:/home# strace cat hello /dev/my_tty1
execve(/bin/cat, [cat, hello], [/* 12 vars */]) = 0
brk(0)
On Tue, 20 Feb 2007 15:50:27 +0300 (MSK)
Mockern [EMAIL PROTECTED] wrote:
Thank you Alan for your respond,
Could you help me with a problem which I have with my tty driver, please?
It does not work with Linux cat operation (but there are no problems to
write, read with select from user
Rik van Riel wrote:
Rik van Riel wrote:
... because I think this is what my patch does :)
Never mind, I see it now.
The attached patch should be correct.
Your patch seems to improve the situation a little bit, but the numbers still
look weird, especially for swap-in, which gets
The tty driver write method is different to the usual fops device write
methods as the buffer is already in kernel space. Clarify the docs since
someone writing a driver made that mistake.
Signed-off-by: Alan Cox [EMAIL PROTECTED]
diff -u --new-file --recursive --exclude-from /usr/src/exclude
On Wed, 2007-02-21 at 14:54 +, Jörn Engel wrote:
On Tue, 20 February 2007 17:46:13 -0800, Vijay Sampath wrote:
The files cfi_cmdset_0002.c and cfi_cmdset_0020.c do not initialize
their wait queues like is done in cfi_cmdset_0001.c. This causes an
oops when the wait queue is accessed.
Tejun Heo wrote:
Pablo Sebastian Greco wrote:
Tejun Heo wrote:
* Pablo, the bug you saw was bad interaction between blacklisted NCQ
device and dynamic queue depth adjustment. Patches are submitted to fix
the problem. Just drop the blacklist patch. Your drives should work
fine in NCQ
On Wed, Feb 21, 2007 at 03:37:29PM +, Alan wrote:
Does this fix the oops ?
Alan
diff -u --new-file --recursive --exclude-from /usr/src/exclude
linux.vanilla-2.6.20-mm2/drivers/ata/pata_pcmcia.c
linux-2.6.20-mm2/drivers/ata/pata_pcmcia.c
---
On Feb 20, 2007, at 9:43 PM, Robert Hancock wrote:
Matthew Fredrickson wrote:
I have noticed something that might be related as well. I am working
on a device driver that would have periodic data errors due to
exceptionally long interrupt handling latency. I have come to the
point that I
On Tue, 2007-02-20 at 23:37 +0100, Michal Piotrowski wrote:
On 20/02/07, Thomas Gleixner [EMAIL PROTECTED] wrote:
On Tue, 2007-02-20 at 19:54 +0100, Michal Piotrowski wrote:
Might it be 6ba9b346e1e0eca65ec589d32de3a9fe32dc5de6 commit?
I doubt that it is, but can you revert it ?
I'm
Update the serial_txx9 driver.
* Use platform_device.
* Fix and cleanup suspend/resume codes.
Signed-off-by: Atsushi Nemoto [EMAIL PROTECTED]
---
diff --git a/drivers/serial/serial_txx9.c b/drivers/serial/serial_txx9.c
index f4440d3..124d056 100644
--- a/drivers/serial/serial_txx9.c
+++
On 21/02/07, Thomas Gleixner [EMAIL PROTECTED] wrote:
On Tue, 2007-02-20 at 23:37 +0100, Michal Piotrowski wrote:
On 20/02/07, Thomas Gleixner [EMAIL PROTECTED] wrote:
On Tue, 2007-02-20 at 19:54 +0100, Michal Piotrowski wrote:
Might it be 6ba9b346e1e0eca65ec589d32de3a9fe32dc5de6
Update: I think that you can ignore this error. I am getting
segmentation faults when I attempt to rebuild the kernel. This is
exactly the same problem I had with slackware 10.1 with the 2.6.10
kernel. So I think it is a hardware issue. Memtest86 didn't show any
errors after 35 passes, so I'll
+static void serial_txx9_initialize(struct uart_port *port)
+{
+ struct uart_txx9_port *up = (struct uart_txx9_port *)port;
+
+ sio_out(up, TXX9_SIFCR, TXX9_SIFCR_SWRST);
+#ifdef CONFIG_CPU_TX49XX
+ /* TX4925 BUG WORKAROUND. Accessing SIOC register
+ * immediately after
On Wed, Feb 21, 2007 at 05:30:10PM +0300, Oleg Nesterov wrote:
Agreed. Note that we don't need the new del_work. It is always safe to
use cancel_work_sync() if we know that the workqueue is frozen, it won't
block. We can also do
if (!cancel_delayed_work())
Thomas Gleixner wrote:
On Tue, 2007-02-20 at 20:53 -0800, Linus Torvalds wrote:
But there's a ton of architecture updates (arm, mips, powerpc, x86, you
name it), ACPI updates, and lots of driver work. And just a lot of
cleanups.
Have fun,
Yup. Fun starts in drivers/net/e1000
e1000 is not
Hello Rodolfo,
Wednesday, February 21, 2007, 4:53:53 PM, you wrote:
Backlight control support for the PXA fram buffer.
Here're some comments: backlight support is already confusing
matter, and your patch IMHO makes it even more confusing for PXAFB.
Before even start with details, let's
Hello,
I'd like to add backlight support for input devices since my custom
board has a backlighted mini keyboard.
It could be acceptable to move the code from drivers/video/backlight/
to drivers/backlight/ renaming the Backlight LCD name into
Backlight and adding two new entries LCD and, maybe,
On Wed, Feb 21, 2007 at 06:00:37PM +0200, Paul Sokolovsky wrote:
On the other hand, there's already
drivers/video/backlight/backlight.c which provides generic BL support,
implemented using notifier callback for FB core. Moreover, there's
My patch _uses_ that support.
corgi_bl.c driver
I have a question about cond_resched().
What is the condition under which I should invoke cond_resched() irreplaceably?
For example, I see the following code in ksoftirqd(),
preempt_enable_no_resched();
cond_resched();
preempt_disable();
But I do not understand why I should not write the
Hello Rodolfo,
Wednesday, February 21, 2007, 6:02:13 PM, you wrote:
Hello,
I'd like to add backlight support for input devices since my custom
board has a backlighted mini keyboard.
There's already generic indicator API, currently mostly known as
[new] LED [classdev] API, even though it
Rodolfo Giometti wrote:
The problem is that sometimes you cannot have a filedescriptor at
all. Think about a PPS source connected with a CPU's GPIO pin. You
have no filedes to use and defining one just for a PPS source or for a
class of PPS sources, I think, is a non sense.
If you have a
On Wed, Feb 21, 2007 at 03:01:54PM +0100, Jean-Luc Coulon (f5ibh) wrote:
At boot time, I've the following messages:
ACPI: PCI Interrupt :00:0f.0[B] GSI 20(level, low) - IRQ 20
sata_via :00:0f.0: failed on iomap PCI BAR 0
sata_via :00:0f.0: out of memory
ACPI: PCI interrupt for
Hello.
In article [EMAIL PROTECTED] (at Tue, 20 Feb 2007 20:53:45 -0800 (PST)),
Linus Torvalds [EMAIL PROTECTED] says:
But there's a ton of architecture updates (arm, mips, powerpc, x86, you
name it), ACPI updates, and lots of driver work. And just a lot of
cleanups.
I cannot boot
Hello Rodolfo,
Wednesday, February 21, 2007, 6:12:10 PM, you wrote:
On Wed, Feb 21, 2007 at 06:00:37PM +0200, Paul Sokolovsky wrote:
On the other hand, there's already
drivers/video/backlight/backlight.c which provides generic BL support,
implemented using notifier callback for FB core.
On Tue, 2007-02-20 at 20:53 -0800, Linus Torvalds wrote:
Ok, the merge window for 2.6.21 has closed, and -rc1 is out there.
There's a lot of changes, as is usual for an -rc1 thing, but at least so
far it would seem that 2.6.20 has been a good base, and I don't think we
have anything
On Wed, 21 Feb 2007 09:16:28 +0100 David Sterba wrote:
(patch against 2.6.21-rc1)
Fix several typos in help text in Kconfig* files.
Signed-off-by: David Sterba [EMAIL PROTECTED]
Looks good except for one item below. Thanks.
diff --git a/crypto/Kconfig b/crypto/Kconfig
index
Greg KH wrote:
This is the start of the stable review cycle for the 2.6.19.5 release.
This will probably be the last release of the 2.6.19-stable series, so
if there are patches that you feel should be applied to that tree,
please let me know.
The attached patch is in 2.6.20 and fixes
On 2/20/07, Jaya Kumar [EMAIL PROTECTED] wrote:
On 2/19/07, Paul Mundt [EMAIL PROTECTED] wrote:
That works for me, though I'd prefer for struct page_list to be done with
a scatterlist, then it's trivial to setup from the workqueue context
without having to shuffle things around.
Ok. Will
Tejun Heo wrote:
Does it work if you give 'irqpoll' kernel parameter?
Yes this works with irqpoll. But as you can see in the attached dmesg
output, now I get a bunch of APIC errors ... ?
Linux version 2.6.20.1 ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115
(prerelease) (Debian 4.1.1-21))
Update: I think that you can ignore this error. I am getting
segmentation faults when I attempt to rebuild the kernel. This is
exactly the same problem I had with slackware 10.1 with the 2.6.10
kernel. So I think it is a hardware issue. Memtest86 didn't show any
errors after 35 passes, so
Greg KH wrote:
This is the start of the stable review cycle for the 2.6.19.5 release.
This will probably be the last release of the 2.6.19-stable series, so
if there are patches that you feel should be applied to that tree,
please let me know.
The attached fixes an oops in the usbnet
On 2/20/07, Geert Uytterhoeven [EMAIL PROTECTED] wrote:
Don't you need a way to specify the maximum deferral time? E.g. a field in
fb_info.
You are right. I will need that. I could put that into struct
fb_deferred_io. So drivers would setup like:
static struct fb_deferred_io hecubafb_defio =
From: Serge E. Hallyn [EMAIL PROTECTED]
Subject: [PATCH] namespaces: update some function names
The {get,exit}_task_namespaces do not grab references to the individual
namespaces, only to the nsproxy. Reflect that in the function names.
Not so important right now, but when pid_ns gets pulled
On Wed, Feb 21, 2007 at 04:48:26PM +, Alan wrote:
Given this costs 1uS in a path that is not performance critical is it
worth putting the #ifdef/#endif in instead of having one set of code that
works for all ?
+ while (sio_in(up, TXX9_SIFCR) TXX9_SIFCR_SWRST)
+ ;
On Wed, 2007-02-21 at 08:24 -0800, Daniel Walker wrote:
The most interesting core change may be the dyntick/nohz one, where timer
ticks will only happen when needed. It's been brewing for a _loong_ time,
but it's in the standard kernel now as an option.
On i386 I get the following,
On Wed, 21 Feb 2007 16:48:26 +, Alan [EMAIL PROTECTED] wrote:
+#ifdef CONFIG_CPU_TX49XX
+ /* TX4925 BUG WORKAROUND. Accessing SIOC register
+* immediately after soft reset causes bus error. */
+ iob();
+ udelay(1);
+#endif
Given this costs 1uS in a path that is not
On Wed, 17 Jan 2007, Andi Kleen wrote:
On Wednesday 17 January 2007 07:31, Chris Wedgwood wrote:
On Tue, Jan 16, 2007 at 08:52:32PM +0100, Christoph Anton Mitterer wrote:
I agree,... it seems drastic, but this is the only really secure
solution.
I'd like to here from Andi how he
I re-checked the code. And this time, I think cond_resched() is useful
while a kernel is compiled with no full preemption function but only
voluntary kernel preemption is enabled (i.e. CONFIG_PREEMPT_VOLUNTARY
is set but CONFIG_PREEMPT is not set). In this case, kernel performs
scheduling at
601 - 700 of 1130 matches
Mail list logo
