On Fri, 9 Mar 2007, Artem Bityutskiy wrote:
Randy Dunlap wrote:
it's clearly a configuration variable, but it's also being used by
itself in a few drivers/net/ source files. is that deliberate?
The ones in drivers/net/ are just local driver debug controls.
They happen to have the
On 3/9/07, Andres Salomon [EMAIL PROTECTED] wrote:
I haven't seen patches in your tree; are you waiting for me to do the
cleanups and resend?
Still in my private tree; will try to push out over the weekend.
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
On Fri, 9 Mar 2007, Dmitry Torokhov wrote:
(II) evdev brain: Rescanning devices (12).
(II) evdev brain: Rescanning devices (13).
(II) evdev brain: Rescanning devices (14).
in this kernel, but I don't know if this is relevant.
After booting back to .20-mm2 everything is
Linus Torvalds wrote:
On Thu, 8 Mar 2007, Bill Davidsen wrote:
Please, could you now rethink plugable scheduler as well? Even if one had to
be chosen at boot time and couldn't be change thereafter, it would still allow
a few new thoughts to be included.
No. Really.
I absolutely
On Thu, 8 Mar 2007 14:52:07 -0800 Luong Ngo wrote:
[...]
static irqreturn board_isr(int irq, void *dev_id, struct pt_regs* regs)
{
spin_lock(dev-lock);
if (dev-irqMask (1 irqBit)) {
// Set the interrupt event mask
dev-irqEvent |= (1 irqBit);
// Disable this irq, it
On Fri, Mar 09, 2007 at 04:19:55AM -0800, Michael K. Edwards wrote:
On 3/8/07, Benjamin LaHaise [EMAIL PROTECTED] wrote:
Any number of things can cause a short write to occur, and rewinding the
file position after the fact is just as bad. A sane app has to either
serialise the writes itself
Note that I am amazed that the kernbench even worked.
The results without slub_debug were not good except for IA64. x86_64 and
ppc64 both blew up for a variety of reasons. The IA64 results were
KernBench Comparison
2.6.21-rc2-mm2-clean
This series of patches extend the alternative instructions framework on
i386 and x86_64 architectures to support two alternative instruction
replacements. This code is used together with the introduction of the
X86_FEATURE_SYNC_RDTSC flag on i386 to simplify and optimize the
get_cycles_sync()
On Friday 09 March 2007, Pekka J Enberg wrote:
From: Serge E. Hallyn [EMAIL PROTECTED]
Make revokeat and frevoke system calls available to user-space on s390.
Signed-off-by: Serge E. Hallyn [EMAIL PROTECTED]
Signed-off-by: Pekka Enberg [EMAIL PROTECTED]
Looks good to me, but you really
From: Joerg Roedel [EMAIL PROTECTED]
This patch extends the alternative instructions framework to support 2
alternative instructions.
Signed-off-by: Joerg Roedel [EMAIL PROTECTED]
--
Joerg Roedel
Operating System Research Center
AMD Saxony LLC Co. KG
diff --git
From: Joerg Roedel [EMAIL PROTECTED]
In this patch updates the x86_64 architecture to work with the changes
to alternative instructions in i386
Signed-off-by: Joerg Roedel [EMAIL PROTECTED]
--
Joerg Roedel
Operating System Research Center
AMD Saxony LLC Co. KG
diff --git
From: Joerg Roedel [EMAIL PROTECTED]
This patch adds the X86_FEATURE_SYNC_RDTSC to the i386 architecture.
This is very helpfull to simplify the get_cycles_sync() function and
remove the #ifdefs from it.
Signed-off-by: Joerg Roedel [EMAIL PROTECTED]
--
Joerg Roedel
Operating System Research
From: Joerg Roedel [EMAIL PROTECTED]
This patch simplifies the get_cycles_sync() function by removing
the #ifdefs from it. Further it introduces an optimization for AMD
processors. There the RDTSCP instruction is used instead of CPUID;RDTSC
which is helpfull if the kernel runs as a KVM guest.
Hi Greg, all,
As the new-style class devices (as opposed to old-style struct
class_device) are becoming more widely used, I noticed that the
dev_printk-based functions are not working properly with these.
New-style class devices have no driver nor bus, almost by definition,
and as a result
On Fri, Mar 09, 2007 at 10:08:05AM +0100, Pavel Machek wrote:
So... if current console is graphical, we leave X accessing the
console... That's bad, because video state is not going to be
restored...?
A graphical console is not necessarily X. Is there any requirement for
there to be a single
Hi Martin,
Martin Schwidefsky wrote:
Yes, please put me or Heiko on CC if you add system calls to s390.
Ok, sorry about that. I would expect akpm to send it to you guys though
whenever revoke graduates from -mm and not merge it to mainline.
Pekka
-
To
On Fri, 2007-03-09 at 16:11 +0100, Arnd Bergmann wrote:
Make revokeat and frevoke system calls available to user-space on s390.
Signed-off-by: Serge E. Hallyn [EMAIL PROTECTED]
Signed-off-by: Pekka Enberg [EMAIL PROTECTED]
Looks good to me, but you really should through Martin, since
Rusty Russell [EMAIL PROTECTED] writes:
__builtin_types_compatible_p() has been around since gcc 2.95, and we
don't use it anywhere. This patch quietly fixes that.
Using BUILD_BUG_ON_ZERO() would have been somewhat cleaner.
-Andi
-
To unsubscribe from this list: send the line unsubscribe
On Fri, 9 Mar 2007, Jiri Kosina wrote:
If this is present also in vanilla and not only in -mm, could you please
try reverting commits 4237081e573b99a48991aa71364b0682c444651c and
d4ae650a904612ffb7edd3f28b69b022988d2466 and let me know if the
situation gets any better?
Hi Jiri,
or even
Matthew Garrett wrote:
On Fri, Mar 09, 2007 at 10:08:05AM +0100, Pavel Machek wrote:
So... if current console is graphical, we leave X accessing the
console... That's bad, because video state is not going to be
restored...?
A graphical console is not necessarily X. Is there any
On Fri, Mar 09, 2007 at 12:13:35PM +0100, Eric Dumazet wrote:
Then just drop the fget_light() 'optimisation' and always take a reference
(atomic on f_count) regardless of single-thread or not. Instead of dirtying
f_light, just do the straightforward thing and be with it.
(that is :
On Fri, 2007-03-09 at 17:41 +0200, Pekka Enberg wrote:
Martin Schwidefsky wrote:
Yes, please put me or Heiko on CC if you add system calls to s390.
Ok, sorry about that. I would expect akpm to send it to you guys though
whenever revoke graduates from -mm and not merge it to mainline.
Yes,
Catalin Marinas [EMAIL PROTECTED] writes:
On 08/03/07, Eric W. Biederman [EMAIL PROTECTED] wrote:
Catalin Marinas [EMAIL PROTECTED] writes:
I think it's only the pid_chain and rcu member that could be placed in
a list and kmemleak scans the memory for these two offsets as well.
I'll check
So far I've tried the simple survive having no handler
for a vector patch and the preliminary 3-patch series
that was in -mm for a while, and neither work on the
Dell PowerEdge 29xx and 19xx systems. These servers
have the Intel 5000X chipset with the 6700PXH PCI Hub
with dual independent PCI-X
[sorry for the dup: this time to the right recipient]
So far I've tried the simple survive having no handler
for a vector patch and the preliminary 3-patch series
that was in -mm for a while, and neither work on the
Dell PowerEdge 29xx and 19xx systems. These servers
have the Intel 5000X chipset
jimmy píše v Pá 09. 03. 2007 v 13:37 +0530:
Alan Cox wrote:
Also note that the word 'chaostables' does not even appear in the patch,
though xt_CHAOS does. Since we know that {xt,ipt}_[A-Z]+ are targets, we
can safely assume that CHAOS does what it says - make fun of nmap.
entropy ?
Robert P. J. Day wrote:
On Fri, 9 Mar 2007, Artem Bityutskiy wrote:
Randy Dunlap wrote:
The ones in drivers/net/ are just local driver debug controls.
They happen to have the same name as a (likely newer) kconfig symbol.
Is there a real problem that needs to be fixed?
Renaming them
Quoting Martin Schwidefsky ([EMAIL PROTECTED]):
On Fri, 2007-03-09 at 17:41 +0200, Pekka Enberg wrote:
Martin Schwidefsky wrote:
Yes, please put me or Heiko on CC if you add system calls to s390.
Ok, sorry about that. I would expect akpm to send it to you guys though
whenever revoke
On Wednesday 07 March 2007 11:55 am, David Brownell wrote:
I'm developing an SPI- bus MMC/SD block driver translation layer.
Another one? There's already been significant work in that area. See for
example
http://marc.theaimsgroup.com/?l=linux-kernelm=117000652529003w=2
Nice, I'll build
On Fri, 9 Mar 2007, Oliver Neukum wrote:
Am Donnerstag, 8. März 2007 17:02 schrieb Alan Stern:
On Thu, 8 Mar 2007, Oliver Neukum wrote:
Hi,
after a lightning bolt from high above I've been looking into refcounting
the data structures drivers use to provide the data used to
On Wed, Mar 07, 2007 at 10:19:05AM +0300, Pavel Emelianov wrote:
Balbir Singh wrote:
Pavel Emelianov wrote:
Introduce generic structures and routines for
resource accounting.
Each resource accounting container is supposed to
aggregate it, container_subsystem_state and its
On Fri, 9 Mar 2007, Mel Gorman wrote:
I'm not sure what you mean by per-order queues. The buddy allocator already
has per-order lists.
Somehow they do not seem to work right. SLAB (and now SLUB too) can avoid
(or defer) fragmentation by keeping its own queues.
-
To unsubscribe from this list:
nobody actually cares about a precise accounting and
calculating shares or partitions of whatever resource,
all that matters is that you have a way to prevent a
potential hostile environment from sucking up all your
resources (or even a single one) resulting in a DoS
This is not true.
There have been various projects attempting to provide resource
management support in Linux, including CKRM/Resource Groups and UBC.
let me note here, once again, that you forgot Linux-VServer
which does quite non-intrusive resource management ...
Herbert, do you care to send patches except
Kirill, responding to Herbert:
do we need or even want that? IMHO the hierarchical
concept CKRM was designed with, was also the reason
for it being slow, unuseable and complicated
1. cpusets are hierarchical already. So hierarchy is required.
I think that CKRM has a harder time doing a
On Thu, 2007-03-08 at 15:08 -0800, Randy Dunlap wrote:
On Thu, 08 Mar 2007 17:58:16 -0500 Mimi Zohar wrote:
This is a request for comments for a new Integrity Based Access
Control(IBAC) LSM module which bases access control decisions
on the new integrity framework services.
2007/3/8, Russell King [EMAIL PROTECTED]:
... which occurs /after/ userspace is up and running, when sysfs is
available. So putting it in sysfs is reasonable.
Is it right place for serial settings?
/sys/class/tty/ttySN/
How far is it reasonable to split termios settings to the attributes?
1)
Quoting [EMAIL PROTECTED] ([EMAIL PROTECTED]):
On Thu, 08 Mar 2007 17:58:16 EST, Mimi Zohar said:
This is a request for comments for a new Integrity Based Access
Control(IBAC) LSM module which bases access control decisions
on the new integrity framework services.
(Hopefully this will
David Woodhouse [EMAIL PROTECTED] writes:
Most system calls seem to get added to i386 first. This patch
automatically generates a warning for any new system call which is
implemented on i386 but not the architecture currently being compiled.
On PowerPC at the moment, for example, it results
On Fri, 2007-03-09 17:11:10 +0100, Andi Kleen [EMAIL PROTECTED] wrote:
David Woodhouse [EMAIL PROTECTED] writes:
Most system calls seem to get added to i386 first. This patch
automatically generates a warning for any new system call which is
implemented on i386 but not the architecture
Eric,
For a longer explanation, see the second part of this e-mail. In
short, the patch below seems to fix this particular leak. I'm not sure
that's the correct/complete fix as I seem to still get a 2nd report.
Any info is welcomed.
diff --git a/drivers/char/tty_io.c b/drivers/char/tty_io.c
Am Freitag, 9. März 2007 17:32 schrieb Alan Stern:
On Fri, 9 Mar 2007, Oliver Neukum wrote:
Am Donnerstag, 8. März 2007 17:02 schrieb Alan Stern:
On Thu, 8 Mar 2007, Oliver Neukum wrote:
Hi,
after a lightning bolt from high above I've been looking into
refcounting
Chuck Ebbert [EMAIL PROTECTED] writes:
[sorry for the dup: this time to the right recipient]
So far I've tried the simple survive having no handler
for a vector patch and the preliminary 3-patch series
that was in -mm for a while, and neither work on the
Dell PowerEdge 29xx and 19xx
On 3/9/07, Jiri Kosina [EMAIL PROTECTED] wrote:
On Fri, 9 Mar 2007, Jiri Kosina wrote:
If this is present also in vanilla and not only in -mm, could you please
try reverting commits 4237081e573b99a48991aa71364b0682c444651c and
d4ae650a904612ffb7edd3f28b69b022988d2466 and let me know if the
On Tue, Mar 06, 2007 at 02:00:36PM -0800, Andrew Morton wrote:
On Tue, 06 Mar 2007 17:55:29 +0300
Pavel Emelianov [EMAIL PROTECTED] wrote:
+struct rss_container {
+ struct res_counter res;
+ struct list_head page_list;
+ struct container_subsys_state css;
+};
+
+struct
Alan Cox wrote:
We must exit immediately on a FIFO fill not take the end of packet path
otherwise each underrun in PIO transmit mode causes a runt packet and the
data is lost.
Signed-off-by: Alan Cox [EMAIL PROTECTED]
applied
-
To unsubscribe from this list: send the line unsubscribe
On 09/03/07, Eric W. Biederman [EMAIL PROTECTED] wrote:
Catalin Marinas [EMAIL PROTECTED] writes:
On 08/03/07, Eric W. Biederman [EMAIL PROTECTED] wrote:
Catalin Marinas [EMAIL PROTECTED] writes:
I think it's only the pid_chain and rcu member that could be placed in
a list and kmemleak
Hi Bryan,
On Fri, 09 Mar 2007 18:13:21 +0800, Wu, Bryan wrote:
Hi folks,
A new structure is added to i2c-core for GPIO-based I2C interface
adapter. My latest GPIO based I2C adapter driver for Blackfin system
will use this stuff. And also IXP4XX GPIO based I2C driver can also be
moved to
On 3/9/07, Oliver Neukum [EMAIL PROTECTED] wrote:
Am Freitag, 9. März 2007 17:32 schrieb Alan Stern:
On Fri, 9 Mar 2007, Oliver Neukum wrote:
Am Donnerstag, 8. März 2007 17:02 schrieb Alan Stern:
On Thu, 8 Mar 2007, Oliver Neukum wrote:
Hi,
after a lightning bolt from high
On Fri, Mar 09, 2007 at 12:13:35PM +0100, Eric Dumazet wrote:
Then just drop the fget_light() 'optimisation' and always take a reference
(atomic on f_count) regardless of single-thread or not. Instead of dirtying
f_light, just do the straightforward thing and be with it.
(that is :
Catalin Marinas [EMAIL PROTECTED] writes:
Eric,
For a longer explanation, see the second part of this e-mail. In
short, the patch below seems to fix this particular leak. I'm not sure
that's the correct/complete fix as I seem to still get a 2nd report.
Any info is welcomed.
Sure. I was
On 3/9/07, Jiri Slaby [EMAIL PROTECTED] wrote:
I don't know if this is related, but my notebook keyboard doesn't emit
numbers with numlock (not even directly Fn+blue number) anymore with
-rc3 (note that LED is flashing when numlock is on). I think -rc2
worked fine (I'm going to check this too).
Please, do not forget look at MAINTAINERS and CC the maintainer. David is CCed.
Amit Choudhary wrote:
Description: Fix error-path leak in function jffs2_scan_medium(), in file
fs/jffs2/scan.c
Signed-off-by: Amit Choudhary [EMAIL PROTECTED]
diff --git a/fs/jffs2/scan.c b/fs/jffs2/scan.c
index
Am Freitag, 9. März 2007 18:02 schrieb Dmitry Torokhov:
I think we already have all refcounting that is needed. What is
missing is subsystem-provided -release() hooks for drivers to release
driver-specific resources when a device finally goes away.
This is an interesting idea. Is it nice to
On Fri, 9 Mar 2007, Mel Gorman wrote:
The results without slub_debug were not good except for IA64. x86_64 and ppc64
both blew up for a variety of reasons. The IA64 results were
Yuck that is the dst issue that Adrian is also looking at. Likely an issue
with slab merging and RCU frees.
Hallo! :-)
Bartlomiej Zolnierkiewicz ha scritto:
Czesc!
On Tuesday 06 March 2007, Marco Lazzarotto wrote:
Ciao!
Bartlomiej Zolnierkiewicz ha scritto:
On Friday 02 March 2007, Pavel Machek wrote:
Hi!
As I reported in bug 8036 in bugzilla.kernel.org,
Hardware Environment:
- Use a
Eric W. Biederman wrote:
Chuck Ebbert [EMAIL PROTECTED] writes:
So far I've tried the simple survive having no handler
for a vector patch and the preliminary 3-patch series
that was in -mm for a while, and neither work on the
Dell PowerEdge 29xx and 19xx systems. These servers
have the
From: Chris Lesiak [EMAIL PROTECTED]
This patch fixes a bug in the cleanup of an spi_bitbang bus. The
workqueue associated with the bus was destroyed before the call to
spi_unregister_master. That meant that spi devices on that bus would be
unable to do IO in their remove method. The shutdown
Hello,
On Mar 9 2007 11:54, Amin Azez wrote:
Adding a member to the ip_conntrack/nf_conntrack and sk_buff struct
would increase the struct sizes, and that would penalize users who do
not intend to use xt_portscan.
I understand what you say but it sounds a bit like saying: but we didn't
make
On 3/9/07, Oliver Neukum [EMAIL PROTECTED] wrote:
Am Freitag, 9. März 2007 18:02 schrieb Dmitry Torokhov:
I think we already have all refcounting that is needed. What is
missing is subsystem-provided -release() hooks for drivers to release
driver-specific resources when a device finally goes
John Rose [EMAIL PROTECTED] wrote on 06.03.2007 22:51:42:
We are seeing several build errors when attempting to apply this to
2.6.21-rc2:
Hot Damn! I did my test compiles with gcc 3.3, and you obviously compiled
with gcc 4.1 - I only got a warning where you got an error, and that
warning
Hi.
I got this message after suspend;resume on my notebook
Clocksource tsc unstable (delta = -154983451 ns)
What other info should I post, who should I Cc?
regards,
--
http://www.fi.muni.cz/~xslaby/Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby
On Friday 09 March 2007 8:55 am, Jean Delvare wrote:
+struct i2c_bitbang_gpio {
+ int sda;
+ int scl;
+};
...
Also, this structure alone isn't very useful. I'm waiting to see
drivers actually making use of it before I will consider merging this
patch at all.
The notion would
Chuck Ebbert [EMAIL PROTECTED] writes:
Eric W. Biederman wrote:
Chuck Ebbert [EMAIL PROTECTED] writes:
So far I've tried the simple survive having no handler
for a vector patch and the preliminary 3-patch series
that was in -mm for a while, and neither work on the
Dell PowerEdge 29xx and
On Friday 09 March 2007 17:11, Benjamin LaHaise wrote:
On Fri, Mar 09, 2007 at 12:13:35PM +0100, Eric Dumazet wrote:
Then just drop the fget_light() 'optimisation' and always take a
reference (atomic on f_count) regardless of single-thread or not. Instead
of dirtying f_light, just do the
On Fri, 9 Mar 2007, Christoph Hellwig wrote:
It was only put in under the premise that they'll fix whatever breaks,
we're not going to put any maintaince border on us to hack around
broken propritary compilers.
Well, since Rusty's macro was hoddible *anyway*, I don't think I'd apply
it
This fixes a lot of whitespace in ibmebus.[ch]
Signed-off-by: Joachim Fenkes [EMAIL PROTECTED]
---
This patchset applies on top of a vanilla 2.6.20 kernel.
No dependencies on other patches except for part 3/3.
This is a repost of my earlier patchset and fixes a stupid
compile error.
This adds two sysfs attributes to /sys/bus/ibmebus which can be used to
notify the ebus driver of added / removed ebus devices in the OF device
tree.
Echoing the device's location code (as found in the OFDT ibm,loc-code
property) into the probe attribute will notify ebus of addition of the
device
* Linus Torvalds [EMAIL PROTECTED] wrote:
Sure, that's clean, From that perspective the apic is a bunch of
registers backed by a state machine or something.
I think you could do much worse than just decide to pick the
IO-APIC/lapic as your virtual interrupt controller model. So I do
This adds uevent support to ibmebus using the generic of_device_uevent()
function.
Signed-off-by: Joachim Fenkes [EMAIL PROTECTED]
---
I split this change into a separate patch because it depends on another
patch against 2.6.20, submitted by Sylvain Munaut:
Mmm.. when it's good, it's *really* good.
My desktop feels snappier and all of that.
No noticeable jerkiness of windows/scrolling,
which I *do* observe with the stock scheduler.
But when it's bad, it stinks.
Like when a make -j2 kernel rebuild is happening in a background window
This is on a
Joerg Roedel wrote:
From: Joerg Roedel [EMAIL PROTECTED]
This patch simplifies the get_cycles_sync() function by removing
the #ifdefs from it. Further it introduces an optimization for AMD
processors. There the RDTSCP instruction is used instead of CPUID;RDTSC
which is helpfull if the kernel
On Fri, 9 Mar 2007, Bill Davidsen wrote:
But it IS okay for people to make special-case schedulers. Because it's MY
machine,
Sure.
Go wild. It's what open-source is all about.
I'm not stopping you.
I'm just not merging code that makes the scheduler unreadable, even hard
to understand,
On Fri, 9 Mar 2007, Eric Dumazet wrote:
CAUTION : d_path() logic is quite tricky.
The correct way to return for example Hello is to put it
at the end of the buffer, and returns a pointer to the first char.
Yeah, it's subtle, since it wants to use a single buffer, and
Mark Lord wrote:
Mmm.. when it's good, it's *really* good.
My desktop feels snappier and all of that.
No noticeable jerkiness of windows/scrolling,
which I *do* observe with the stock scheduler.
But when it's bad, it stinks.
Like when a make -j2 kernel rebuild is happening in a background
Hi,
I get a lot of
NOHZ: local_softirq_pending 02
and I have noticed some swsuspend problems.
Disabling non-boot CPUs ...
CPU1 playing dead
[c0105114] dump_trace+0x7f/0x229
[c0105397] show_trace_log_lvl+0x35/0x54
[c01053e2] show_trace+0x2c/0x2e
[c0105515] dump_stack+0x29/0x2b
[c010213a]
On Fri, 9 Mar 2007, Ingo Molnar wrote:
yes - but we already support the raw hardware ABI, in the native kernel.
Why do you continue to call paravirt an ABI?
We got over that. It's not. It's an API.
VMI is an ABI.
As long as you try to confuse the two, there's no point to the discussion.
On Fri, Mar 09, 2007 at 07:39:05PM +1100, Con Kolivas wrote:
On Friday 09 March 2007 19:20, Matt Mackall wrote:
And I've just rebooted with NO_HZ and things are greatly improved. At
idle, Beryl effects are silky smooth (possibly better than stock) and
shows less load. Under 'make', Beryl is
On Friday 09 March 2007 19:02, Ingo Molnar wrote:
_1463_ hooks, spread out all around the x86 arch.
They are not all different hooks though, just many call site of the same.
Also most of them are well defined to just match what the instructions
do.
paravirt_ops has under hundred entries right
On Thu, Mar 08, 2007 at 11:01:57PM +0100, Jan Engelhardt wrote:
On Mar 8 2007 22:25, Sam Ravnborg wrote:
Subject: Re: [PATCH] Fix building kernel under Solaris
Since Solaris seems to be on the run, I did myself try compile it.
However, unlike the original poster who said he did so on
* Ingo Molnar ([EMAIL PROTECTED]) wrote:
i claim that when the 'API cut' is done at the right level then no more
than say 100 hooks would be needed - with virtually zero kernel size
increase. We've got all the right highlevel abstractions: genirq, gtod,
clockevents. Whatever is missing at
On Fri, 2007-09-03 at 15:34 +, Matthew Garrett wrote:
On Fri, Mar 09, 2007 at 10:08:05AM +0100, Pavel Machek wrote:
So... if current console is graphical, we leave X accessing the
console... That's bad, because video state is not going to be
restored...?
A graphical console is not
We (the -stable team) are announcing the release of the 2.6.20.2 kernel.
It contains a metric buttload of bugfixes and security updates, so all
2.6.20 users are recommended to upgrade.
The diffstat and short summary of the fixes are below.
I'll also be replying to this message with a copy of the
This is a very simple bitbanging i2c bus driver utilizing the new
arch-neutral GPIO API. Useful for chips that don't have a built-in
i2c controller, additional i2c busses, or testing purposes.
To use, include something similar to the following in the
board-specific setup code:
#include
On Thu, March 8, 2007 11:28 pm, Len Brown wrote:
On Monday 05 March 2007 05:35, Antonino A. Daplas wrote:
Looks like I got fooled by the negative logic for the nvidia_bugs().
Please test this patch -- it should fix it,
as well as simplify the code a bit.
thanks, -Len
Yep. You can knock
* Linus Torvalds [EMAIL PROTECTED] wrote:
On Fri, 9 Mar 2007, Ingo Molnar wrote:
yes - but we already support the raw hardware ABI, in the native
kernel.
Why do you continue to call paravirt an ABI?
We got over that. It's not. It's an API.
VMI is an ABI.
Unfortunately i still
On Friday 09 March 2007 10:48 am, Haavard Skinnemoen wrote:
This is a very simple bitbanging i2c bus driver utilizing the new
arch-neutral GPIO API. Useful for chips that don't have a built-in
i2c controller, additional i2c busses, or testing purposes.
That's the right idea! But remember that
On Fri, 9 Mar 2007, Dmitry Torokhov wrote:
On 3/9/07, Oliver Neukum [EMAIL PROTECTED] wrote:
Am Freitag, 9. März 2007 18:02 schrieb Dmitry Torokhov:
I think we already have all refcounting that is needed. What is
missing is subsystem-provided -release() hooks for drivers to release
On Friday, 9 March 2007 13:29, Heiko Carstens wrote:
On Wed, Mar 07, 2007 at 09:07:17PM +, Pavel Machek wrote:
Hi!
Prevent the WARN_ON() in
arch/x86_64/kernel/acpi/sleep.c:init_low_mapping()
from triggering by disabling nonboot CPUs before we finally enter the
platform
From: Cliff Wickman [EMAIL PROTECTED]
(this is a second submission -- the first was from a work area back
porting to an older release)
When a cpu is disabled, move_task_off_dead_cpu() is called for tasks
that have been running on that cpu.
Currently, such a task is migrated:
1) to any cpu on
On 3/9/07, Sergey Vlasov [EMAIL PROTECTED] wrote:
On Thu, 8 Mar 2007 14:52:07 -0800 Luong Ngo wrote:
[...]
static irqreturn board_isr(int irq, void *dev_id, struct pt_regs* regs)
{
spin_lock(dev-lock);
if (dev-irqMask (1 irqBit)) {
// Set the interrupt event mask
On Fri, 9 Mar 2007, Ingo Molnar wrote:
Unfortunately i still dont see where i'm wrong, and i'm really trying to
understand your argument. Is your argument that as long as an ABI (VMI)
is never directly used but only used via wrapper functions
(paravirt_ops)
No.
My argument is utternly
Benjamin Herrenschmidt wrote:
- radeonfb_pm_init(rinfo, rinfo-is_mobility ? 1 : -1,
ignore_devlist, force_sleep);
+ radeonfb_pm_init(rinfo, rinfo-is_mobility rinfo-family !=
CHIP_FAMILY_RS480 ? 1 : -1, ignore_devlist, force_sleep);
I'd rather you add a check for
Hi,
On Friday, 9 March 2007 09:54, Pavel Machek wrote:
Hi!
Index: linux-2.6.21-rc2-mm2/kernel/power/disk.c
===
--- linux-2.6.21-rc2-mm2.orig/kernel/power/disk.c
+++ linux-2.6.21-rc2-mm2/kernel/power/disk.c
@@
Am Freitag, 9. März 2007 20:32 schrieb Alan Stern:
On Fri, 9 Mar 2007, Dmitry Torokhov wrote:
On 3/9/07, Oliver Neukum [EMAIL PROTECTED] wrote:
Am Freitag, 9. März 2007 18:02 schrieb Dmitry Torokhov:
I think we already have all refcounting that is needed. What is
missing is
On Fri, 9 Mar 2007, Alan Stern wrote:
Oliver, your idea won't work either. Think about what would happen if
someone did
rmmod driver_module /sys/devices/.../attribute_file
The rmmod process would never actually read the attribute, so until it
exited the private data structure
On Fri, Mar 09, 2007 at 11:30:12AM -0800, David Brownell wrote:
On Friday 09 March 2007 10:48 am, Haavard Skinnemoen wrote:
This is a very simple bitbanging i2c bus driver utilizing the new
arch-neutral GPIO API. Useful for chips that don't have a built-in
i2c controller, additional i2c
* Linus Torvalds [EMAIL PROTECTED] wrote:
Similarly, maybe the VMI ABI doesn't allow for something that the
kernel wants to do efficiently. Big deal. What relevance does that
have to do with anything, except the fact that if true, the VMWare
people are screwed? It's *their* problem.
i
On Saturday 10 March 2007 05:27, Matt Mackall wrote:
On Fri, Mar 09, 2007 at 07:39:05PM +1100, Con Kolivas wrote:
On Friday 09 March 2007 19:20, Matt Mackall wrote:
And I've just rebooted with NO_HZ and things are greatly improved. At
idle, Beryl effects are silky smooth (possibly better
On Mar 9 2007 20:00, Sam Ravnborg wrote:
On Thu, Mar 08, 2007 at 11:01:57PM +0100, Jan Engelhardt wrote:
Since Solaris seems to be on the run, I did myself try compile it.
However, unlike the original poster who said he did so on SunOS 4.8, I
did it on 5.11_snv39, yielding a bigger
101 - 200 of 1046 matches
Mail list logo
