On Sat, May 26, 2007 at 10:18:54PM +0200, bert hubert wrote:
> Greg, Kay, kernel people,
>
> Today I booted 2.6.22-rc2 on Ubunty Edgy Eft, and lsusb died on me:
>
> [EMAIL PROTECTED]:~$ lsusb
> [EMAIL PROTECTED]:~$ sudo lsusb
> [EMAIL PROTECTED]:~$
>
> This behaviour persists in rc4. This
On May 26, 2007, at 22:37:02, [EMAIL PROTECTED] wrote:
On Sat, 26 May 2007 22:10:34 EDT, Kyle Moffett said:
On May 26, 2007, at 19:08:56, Toshiharu Harada wrote:
(1) Object labeling has a assumption that labels are always
properly defined and maintained. This can not be easily achieved.
Hi Cédric,
On Saturday 26 May 2007 17:25, Cédric Augonnet wrote:
> Hi,
>
> When trying to load input_polldev compiled as a module on my
> 2.6.22-rc2-mm1 kernel, it is impossible because of some symbols that
> are said to be missing :
>
> [EMAIL PROTECTED]:~$ sudo modprobe input_polldev
> FATAL:
On 5/26/07, Nitin Gupta <[EMAIL PROTECTED]> wrote:
Hi Bret,
On 5/25/07, Bret Towe <[EMAIL PROTECTED]> wrote:
>
> [ 237.556167] LZO compress successful: orig_size=17448, comp_size=8183
> [ 253.320760] LZO decompress successful: decomp_size=17448
>
> 2221c586e3eb869af7f4333d4f56b441b9aa8414
Here is a patch against 2.6.22-rc3 that adds support for both the PATA
and SATA portions of the Marvell AHCI-like chip.
The architecture for PATA is quite nice, mimicing AHCI very closely.
Basic port scanning, interrupt handling, freezing and thawing is the
same, and uses the same register
On Fri, May 25, 2007 at 03:37:46PM -0300, Rodrigo Pereira wrote:
> (sorry my English)
>
> I'm helping M?rton N?meth in a experimental mail led driver
> leds-clevo-mail.c for clevo laptops and I have problems with this
> driver:
> this files
> /sys/class/trigger, /sys/class//dalay_on and
>
Ingo Molnar wrote:
i'm pleased to announce release -v14 of the CFS scheduler patchset.
The CFS patch against v2.6.22-rc2, v2.6.21.1 or v2.6.20.10 can be
downloaded from the usual place:
http://people.redhat.com/mingo/cfs-scheduler/
I tried this on 2.6.21.1, Good work!
I have a
Bill Davidsen wrote:
I was testing susp2disk in 2.6.21.1 under FC6, to support reliable
computing environment (RCE) needs. The idea is that if power fails,
after some short time on UPS the system does susp2disk with a time set,
and boots back every so often to see if power is stable.
No, I
On Sat, 2007-05-26 at 22:18 +0200, bert hubert wrote:
> Today I booted 2.6.22-rc2 on Ubunty Edgy Eft, and lsusb died on me:
>
> [EMAIL PROTECTED]:~$ lsusb
> [EMAIL PROTECTED]:~$ sudo lsusb
> [EMAIL PROTECTED]:~$
>
> This behaviour persists in rc4. This might be udev related. I'm running:
> ii
On Sat, 26 May 2007 22:10:34 EDT, Kyle Moffett said:
> On May 26, 2007, at 19:08:56, Toshiharu Harada wrote:
> > (1) Object labeling has a assumption that labels are always
> > properly defined and maintained. This can not be easily achieved.
>
> That's a circular argument, and a fairly
David Miller wrote:
>
>> i presume then i shouldn't be using IRQF_SHARED, if using MSI.
>
> That's actually a really good question.
>
> It is likely architecture dependant whether the PCI controller wires
> unique MSI interrupts to shared cpu interrupt lines.
>
> I can imagine many systems
On Sun, May 27, 2007 at 12:55:30AM +0100, David Howells wrote:
> J. Bruce Fields <[EMAIL PROTECTED]> wrote:
>
> > > + if (!afs_lock_manager) {
> > > + afs_lock_manager = create_singlethread_workqueue("kafs_lockd");
> > > + if (!afs_lock_manager)
> > > + return
On May 26, 2007, at 19:08:56, Toshiharu Harada wrote:
2007/5/27, James Morris <[EMAIL PROTECTED]>:
On Sat, 26 May 2007, Kyle Moffett wrote:
AppArmor). On the other hand, if you actually want to protect
the _data_, then tagging the _name_ is flawed; tag the *DATA*
instead.
Bingo.
(This
On Sun, May 27, 2007 at 05:01:02AM +0400, Manu Abraham wrote:
> David Miller wrote:
> > True, on sparc64 PCI-E controllers, for example, the MSI vector is
> > received by the PCI-E host controller, and the host controller turns
> > this into a cpu format interrupt packet for the system bus.
>
>
On Sun, 27 May 2007 02:20:52 +0200
Adrian Bunk <[EMAIL PROTECTED]> wrote:
> On Sat, May 26, 2007 at 05:01:04PM -0500, Jay Cliburn wrote:
> >
> > The Via VT3351 APIC does not play well with MSI and unleashes a
> > flood of APIC errors when MSI is used to deliver interrupts. The
> > problem was
On Sat, 26 May 2007 15:58:50 PDT, Casey Schaufler said:
> Fair enough, I don't believe that an argv[0] check ought to
> be used as a security mechanism. I am not convinced that everyone
> would agree with us.
Having seen my share of argv[0]-related security bugs in my years, I have to
agree that
William Lee Irwin III wrote:
Srivatsa Vaddagiri wrote:
Ingo/Peter, any thoughts here? CFS and smpnice probably is "broken"
with respect to such example as above albeit for nice-based tasks.
On Sat, May 26, 2007 at 10:17:42AM +1000, Peter Williams wrote:
See above. I think that faced with
David Miller wrote:
> From: Grant Grundler <[EMAIL PROTECTED]>
> Date: Sat, 26 May 2007 18:16:31 -0600
>
>> Are they really? The device is generating the transaction on the bus.
>> The PCI host controller (in general) will be routing that transaction
>> to wherever the "dest addr" of the MSI
Michal Piotrowski wrote:
> File systems
>
> Subject: 2.6.21-git10/11: files getting truncated on xfs
> References : http://lkml.org/lkml/2007/5/9/410
> Submitter : Jeremy Fitzhardinge <[EMAIL PROTECTED]>
> Handled-By : David Chinner <[EMAIL PROTECTED]>
> Patch :
From: Grant Grundler <[EMAIL PROTECTED]>
Date: Sat, 26 May 2007 18:16:31 -0600
> Are they really? The device is generating the transaction on the bus.
> The PCI host controller (in general) will be routing that transaction
> to wherever the "dest addr" of the MSI lives. It doesn't have to be
> in
On Sat, May 26, 2007 at 05:01:04PM -0500, Jay Cliburn wrote:
>
> The Via VT3351 APIC does not play well with MSI and unleashes a flood
> of APIC errors when MSI is used to deliver interrupts. The problem
> was recently exposed when the atl1 network device driver, which enables
> MSI by default,
H. Peter Anvin wrote:
> Pardon me for saying it, but it's hardly a hardship to add support for a
> single additional constant in existing code. I'm starting to think this
> argument is approaching not just the silly, but downright ridiculous.
>
Well, if the existing code is a standard
On Sat, May 26, 2007 at 05:00:39PM -0700, David Miller wrote:
> From: Grant Grundler <[EMAIL PROTECTED]>
> Date: Sat, 26 May 2007 17:55:15 -0600
>
> > MSI (and MSI-X) vectors are required to be exclusive.
> > I submitted that change to pci.txt last year:
> > http://lkml.org/lkml/2006/12/25/2
Rusty Russell wrote:
>
> hpa wrote:
>> Do we have *any* environment that enters the 32-bit code with interrupts
>> enabled? I would think that is unsafe no matter how you do it.
>
> Yeah, the cli there seems strange: maybe it's safe to simply delete it?
>
I suspect it was simply put there as
Jeremy Fitzhardinge wrote:
>
> I'd really prefer to keep an intact embedded ELF file rather than have a
> semi-ELF file. That way it would be easier to simply load the image and
> point the normal ELF machinery at some offset into the file rather than
> having to have a special handler for
Kyle Moffett <[EMAIL PROTECTED]> wrote:
> I was actually under the impression that OpenAFS had support for byte-
> range locking (as well as lock upgrade/downgrade);
As far as I know, there is no support for byte-range locking at all in the AFS
protocol itself. The client can try to emulate
On Sun, 2007-05-27 at 00:47 +0100, Jeremy Fitzhardinge wrote:
> Rusty Russell wrote:
> > You also want to skip the cli: perhaps a separate flag for this is
> > appropriate though.
> >
>
> Not a problem for Xen; it will be trapped+emulated (ie, ignored).
Well, I could do that for lguest as a
From: Grant Grundler <[EMAIL PROTECTED]>
Date: Sat, 26 May 2007 17:55:15 -0600
> MSI (and MSI-X) vectors are required to be exclusive.
> I submitted that change to pci.txt last year:
> http://lkml.org/lkml/2006/12/25/2
>
> and ISTR I've posted that bit of the PCI spec a few years ago.
>
J. Bruce Fields <[EMAIL PROTECTED]> wrote:
> > + if (!afs_lock_manager) {
> > + afs_lock_manager = create_singlethread_workqueue("kafs_lockd");
> > + if (!afs_lock_manager)
> > + return -ENOMEM;
> > + }
> > + return 0;
>
> Doesn't this need some
On Sat, May 26, 2007 at 03:49:10PM -0700, David Miller wrote:
> From: Manu Abraham <[EMAIL PROTECTED]>
> Date: Sat, 26 May 2007 19:03:12 +0400
>
> > i presume then i shouldn't be using IRQF_SHARED, if using MSI.
>
> That's actually a really good question.
>
> It is likely architecture dependant
This patch is an attempt to convert sata_qstor over to new EH.
It compiles, but I have not tested it. If anyone is willing to give
it an "it talks to the disks" test that would be great.
This is checked into the 'new-eh' branch of libata. Review requested.
drivers/ata/sata_qstor.c | 65
(sorry about the long Cc: list for such a trivial patch, but I wanted to
include everyone who's stuff I'm changing)
The UMSDOS filesystem was removed back in 2.6.11, but some tiny bits
stuck around. This patch removes the few leftovers.
The only things left behind after this are the entries in
Not in the ABI doc, is there and doc at all, and if not could someone
who knows where it's used might give me a hint, as a quick look didn't
bring enlightenment. Or is it a future hook which doesn't work yet?
--
Bill Davidsen <[EMAIL PROTECTED]>
"We have more to fear from the bungling of the
Eric W. Biederman wrote:
>> What was the problem with ELF bzImage? Is it confirmed to be
>> problematic, or just suspected?
>>
>
> There was a problem, Andrews machine would not the kernel with the ELF
> header. It was not root caused. So we are not certain why.
>
The Vaio? Do you
Rusty Russell wrote:
> You also want to skip the cli: perhaps a separate flag for this is
> appropriate though.
>
Not a problem for Xen; it will be trapped+emulated (ie, ignored).
J
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
H. Peter Anvin wrote:
> Robert P. J. Day wrote:
>> It does not make sense for a noreturn function to have a return type
>> other than void.
>> ^
>> ===
>>
>> so I'm just going to stick with the pattern that's been used so
From: Divy Le Ray <[EMAIL PROTECTED]>
Bump FW version to 4.1.
Modify chip tuning in consequence.
Signed-off-by: Divy Le Ray <[EMAIL PROTECTED]>
---
drivers/net/cxgb3/regs.h|4
drivers/net/cxgb3/t3_hw.c | 40 ++--
drivers/net/cxgb3/version.h
Michael Buesch wrote:
On Sunday 27 May 2007 01:00:04 [EMAIL PROTECTED] wrote:
From: Divy Le Ray <[EMAIL PROTECTED]>
Bump FW version to 4.1.
Modify chip tuning in consequence.
Signed-off-by: Divy Le Ray <[EMAIL PROTECTED]>
---
@@ -2496,11 +2500,11 @@ static void __devinit
2007/5/27, James Morris <[EMAIL PROTECTED]>:
On Sat, 26 May 2007, Kyle Moffett wrote:
> AppArmor). On the other hand, if you actually want to protect the _data_,
> then tagging the _name_ is flawed; tag the *DATA* instead.
Bingo.
(This is how traditional Unix DAC has always functioned, and is
This patch is an attempt to convert pdc_adma over to new EH. It
compiles, but I have not tested it. If anyone is willing to give it an
"it talks to the disks" test that would be great.
This hardware is -mostly- compatible with the docs on
http://www.T13.org/ (look for d1510r1) according to
On Sunday 27 May 2007 01:00:04 [EMAIL PROTECTED] wrote:
> From: Divy Le Ray <[EMAIL PROTECTED]>
>
> Bump FW version to 4.1.
> Modify chip tuning in consequence.
>
> Signed-off-by: Divy Le Ray <[EMAIL PROTECTED]>
> ---
> @@ -2496,11 +2500,11 @@ static void __devinit init_mtus(unsigned
>*
> Hello all,
>
> I want to know in detail about , what the events (epoll or /dev/poll or
> select ) achieve in contrast to thread per client.
>
> i can have a thread per client and use send and recv system call directly
> right? Why do i go for these event mechanisms?
>
> Please help me to
From: Divy Le Ray <[EMAIL PROTECTED]>
Rx traffic needs to be halted when the MTU is changed
to avoid a potential chip hang.
Reset/restore MAC filters around a MTU change.
Also fix the pause frames high materwark setting.
Signed-off-by: Divy Le Ray <[EMAIL PROTECTED]>
---
From: Divy Le Ray <[EMAIL PROTECTED]>
Fix variables initialization and usage in the MAC watchdog.
Signed-off-by: Divy Le Ray <[EMAIL PROTECTED]>
---
drivers/net/cxgb3/xgmac.c | 31 +--
1 files changed, 21 insertions(+), 10 deletions(-)
diff --git
From: Divy Le Ray <[EMAIL PROTECTED]>
The chip executes microcode present in internal RAM,
whose content is loaded from EEPROM on power cycle.
This patch allows an update of the microcode through PIO
without forcing a power cycle.
Signed-off-by: Divy Le Ray <[EMAIL PROTECTED]>
---
From: Divy Le Ray <[EMAIL PROTECTED]>
Fix netpoll handler to work with line interrupt, msi and msi-x.
Signed-off-by: Divy Le Ray <[EMAIL PROTECTED]>
---
drivers/net/cxgb3/cxgb3_main.c | 12 +---
drivers/net/cxgb3/sge.c|1 -
2 files changed, 9 insertions(+), 4 deletions(-)
From: Divy Le Ray <[EMAIL PROTECTED]>
Check all lanes for link status on direct XAUI cards.
Don't assume that direct XAUI always uses XGMAC 1.
Signed-off-by: Divy Le Ray <[EMAIL PROTECTED]>
---
drivers/net/cxgb3/ael1002.c | 10 --
drivers/net/cxgb3/regs.h|2 ++
2 files
From: Divy Le Ray <[EMAIL PROTECTED]>
Bump FW version to 4.1.
Modify chip tuning in consequence.
Signed-off-by: Divy Le Ray <[EMAIL PROTECTED]>
---
drivers/net/cxgb3/regs.h|4
drivers/net/cxgb3/t3_hw.c | 42 +++---
From: Divy Le Ray <[EMAIL PROTECTED]>
Streamline page management on RX.
Fix dma mappings.
Signed-off-by: Divy Le Ray <[EMAIL PROTECTED]>
---
drivers/net/cxgb3/adapter.h | 38 ++--
drivers/net/cxgb3/sge.c | 425 ++-
2 files changed, 233
Hi Jeff,
I'm submitting a set of bug fixes for inclusion in 2.6.22.
The patches are built against Linus'git tree.
Here is a brief description:
- Fix page management in the SGE code,
- Fix netpoll handler,
- Fix link status detection for direct XAUI adapters,
- Update FW to 4.1 and proceed to
--- Andreas Gruenbacher <[EMAIL PROTECTED]> wrote:
> On Friday 25 May 2007 21:06, Casey Schaufler wrote:
> > --- Jeremy Maitin-Shepard <[EMAIL PROTECTED]> wrote:
> > > ...
> > > Well, my point was exactly that App Armor doesn't (as far as I know) do
> > > anything to enforce the argv[0]
David Miller wrote:
> From: Manu Abraham <[EMAIL PROTECTED]>
> Date: Sat, 26 May 2007 19:03:12 +0400
>
>> i presume then i shouldn't be using IRQF_SHARED, if using MSI.
>
> That's actually a really good question.
>
> It is likely architecture dependant whether the PCI controller wires
> unique
From: Manu Abraham <[EMAIL PROTECTED]>
Date: Sat, 26 May 2007 19:03:12 +0400
> i presume then i shouldn't be using IRQF_SHARED, if using MSI.
That's actually a really good question.
It is likely architecture dependant whether the PCI controller wires
unique MSI interrupts to shared cpu
I was testing susp2disk in 2.6.21.1 under FC6, to support reliable
computing environment (RCE) needs. The idea is that if power fails,
after some short time on UPS the system does susp2disk with a time set,
and boots back every so often to see if power is stable.
No, I don't want susp2mem
From: Uwe Bugla <[EMAIL PROTECTED]>
Date: Sat, 26 May 2007 12:40:54 +0200
> Am Samstag, 26. Mai 2007 07:00 schrieben Sie:
> > Try it again, please.
>
> NO!
Your not a nice person, and consistently so, therefore you can't post
to the mailing lists I run any more.
-
To unsubscribe from this list:
On 5/26/07, Jan Engelhardt <[EMAIL PROTECTED]> wrote:
Based in part on Auke's patch.
Signed-off-by: Jan Engelhardt <[EMAIL PROTECTED]>
---
Documentation/CodingStyle | 74 +++---
1 file changed, 64 insertions(+), 10 deletions(-)
Index:
Am Samstag 26 Mai 2007 schrieb Rafael J. Wysocki:
Hi Rafael!
> The outcome was, more-or-less, that we'll work on merging suspend2 or
> at least some parts of it.
>
> However, in the meantime there have been some discussions implying that
> we have some important problems with suspend/hibernation
Am Samstag, 26. Mai 2007 23:52 schrieben Sie:
> On Sat, 2007-05-26 at 23:32 +0200, Uwe Bugla wrote:
> > Am Samstag, 26. Mai 2007 21:49 schrieben Sie:
> > > On Saturday 26 May 2007 21:39:54 Uwe Bugla wrote:
> > > > Am Samstag, 26. Mai 2007 21:19 schrieben Sie:
> > > > > Uwe, please try the
On Sat, 2007-05-26 at 10:52 +0200, Geert Uytterhoeven wrote:
> On Sat, 26 May 2007, Benjamin Herrenschmidt wrote:
> > On Fri, 2007-05-25 at 13:24 +0200, Olaf Hering wrote:
> > > On Fri, May 25, [EMAIL PROTECTED] wrote:
> > >
> > > > +++ b/drivers/scsi/ps3rom.c
> > >
> > > > +
On Sat, 2007-05-26 at 10:51 +0200, Geert Uytterhoeven wrote:
>
> I know.
>
> Do you know another way to allocate an aligned chunk of 256 KiB of
> physically
> contiguous memory, possibly a long time after boot up?
kmalloc & a good prayer ? :-0
Ben.
-
To unsubscribe from this list: send the
Hi,
Following the "Freezing of kernel threads" discussion
(http://lkml.org/lkml/2007/5/12/162) I have created a patch that changes the
freezer's behavior with respect to kernel threads. Namely, with the patch
applied all kernel threads are nonfreezable by default (have PF_NOFREEZE set)
and the
Michal,
thanks! Using 2.6.21.3 cured the problem.
The fix was mentioned in the changelog of 2.6.21.2
Uli
--
Ulrich Mayer
Michal Piotrowski schrieb:
Hi Ulrich,
On 26/05/07, Ulrich Mayer <[EMAIL PROTECTED]> wrote:
A couple of days ago I sent a note to Ingo Molnar with the following bug
Hi,
> > On Thursday 24 May 2007 16:50, Emmanuel Fusté wrote:
> > > This bios is full of bugs, a real plague. Will try to quirk
> > > this register at boot time.
I tried, but it did not change the behavior of the loop command.
Will stick with i8042.noloop as boot parameter.
Thank you for your
The Via VT3351 APIC does not play well with MSI and unleashes a flood
of APIC errors when MSI is used to deliver interrupts. The problem
was recently exposed when the atl1 network device driver, which enables
MSI by default, stimulated APIC errors on an Asus M2V mainboard, which
employs the Via
On Saturday 26 May 2007 23:32:50 Uwe Bugla wrote:
> Hint: Although being a "non-hacker" or "non-developer" I do have stepped
...
> In so far, if you continue to state that debugging is nothing but guessing
> around wildly you are definitely wrong, showing us all your missing code
> hacker
"Robert P. J. Day" <[EMAIL PROTECTED]> writes:
> that's not true, AFAICT. the pattern seems to be that, in the case of
> declarations, attributes go at the end, as in:
Anyway, that attribute has to be in the declarations as without it
there the compiler can't optimize the callers.
--
Krzysztof
On Sat, 2007-05-26 at 23:32 +0200, Uwe Bugla wrote:
> Am Samstag, 26. Mai 2007 21:49 schrieben Sie:
> > On Saturday 26 May 2007 21:39:54 Uwe Bugla wrote:
> > > Am Samstag, 26. Mai 2007 21:19 schrieben Sie:
> > > > Uwe, please try the following patch:
> > > >
> > > > Index:
Dave Dillow wrote:
On Sat, 2007-05-26 at 16:56 -0400, Jeff Garzik wrote:
Dave, any chance you could try 2.6.22-rc3 + my v4 patch, on a different
hard drive? Preferably a non-Maxtor, or at least not another Maxtor
6L200S0. If that's a big deal, don't worry about it. I just want to
rule out
Am Samstag, 26. Mai 2007 21:49 schrieben Sie:
> On Saturday 26 May 2007 21:39:54 Uwe Bugla wrote:
> > Am Samstag, 26. Mai 2007 21:19 schrieben Sie:
> > > Uwe, please try the following patch:
> > >
> > > Index: bu3sch-wireless-dev/drivers/net/b44.c
> > >
Hi.
On Sat, 2007-05-26 at 14:49 +0200, Maximilian Engelhardt wrote:
> On Saturday 26 May 2007, Nigel Cunningham wrote:
> > Hi.
> >
> > On Sat, 2007-05-26 at 11:28 +0200, Maximilian Engelhardt wrote:
> > > Hello,
> > >
> > > When I try software suspend on my laptop it always returns to my running
Thomas Gleixner wrote:
> On Fri, 2007-05-25 at 21:58 +0100, Rui Nuno Capela wrote:
>> Is there anything I can do better to help myself figuring out this
>> issue? As this is a modern laptop such things like a serial console are
>> unavailable, but it would be nice to track things up over
On Sat, 2007-05-26 at 16:56 -0400, Jeff Garzik wrote:
> Dave, any chance you could try 2.6.22-rc3 + my v4 patch, on a different
> hard drive? Preferably a non-Maxtor, or at least not another Maxtor
> 6L200S0. If that's a big deal, don't worry about it. I just want to
> rule out buggy
On Saturday 26 May 2007 22:33:13 Uwe Bugla wrote:
> Am Samstag, 26. Mai 2007 21:57 schrieben Sie:
> > Uwe Bugla wrote:
> > > OK, applied this one against 2.6.22-rc3, assuming a typo error by you,
> > > Andrew.
> > >
> > > Result is: No change: non functionable b44 device!
> >
> > Could you please
dean gaudet wrote:
On Fri, 25 May 2007, Jeff Garzik wrote:
Already uncovered and fixed a few bugs in v3.
Here's v4 of the sata_mv new-EH patch.
you asked for test results with 2.6.21.3 ... that seems to boot fine,
and i've tested reading from the disks only and it seems to be working
fine.
Greg, Kay, kernel people,
Today I booted 2.6.22-rc2 on Ubunty Edgy Eft, and lsusb died on me:
[EMAIL PROTECTED]:~$ lsusb
[EMAIL PROTECTED]:~$ sudo lsusb
[EMAIL PROTECTED]:~$
This behaviour persists in rc4. This might be udev related. I'm running:
ii udev
Rusty Russell wrote:
>>
>> + Bit 6 (write): KEEP_SEGMENTS
>> +Protocol: 2.07+
>> +- if 0, reload the segment registers in the 32bit entry point.
>> +- if 1, do not reload the segment registers in the 32bit entry point.
>> +Assume that %cs %ds %ss %es are all set to flat
2007/5/14, Satyam Sharma <[EMAIL PROTECTED]>:
On 5/14/07, Dmitry Torokhov <[EMAIL PROTECTED]> wrote:
> Hi Satyam,
>
> On Saturday 12 May 2007 01:45, Satyam Sharma wrote:
> > Seems to be good-looking code!
>
> Thanks. Do you have the hardware? Were you able to test the patch?
Oh, sorry, no. I
Am Samstag, 26. Mai 2007 21:57 schrieben Sie:
> Uwe Bugla wrote:
> > OK, applied this one against 2.6.22-rc3, assuming a typo error by you,
> > Andrew.
> >
> > Result is: No change: non functionable b44 device!
>
> Could you please send the following:
>
> 1. the output of lsmod from the
On Saturday, 26 May 2007 19:37, Martin Steigerwald wrote:
> Am Mittwoch 25 April 2007 schrieb Pavel Machek:
> > Hi!
> >
> > > This is why there's a lot to be said for
> > >
> > > echo mem > /sys/power/state
> > >
> > > and being able to follow the path through _one_ object (the kernel)
> > >
Larry Finger <[EMAIL PROTECTED]> :
[...]
> 2. the output of dmesg from the non-functioning kernel
>
> 3. your .config used to create your non-functioning kernel.
They are already in the thread.
--
Ueimor
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Saturday, 26 May 2007 13:55, Herbert Xu wrote:
> On Sat, May 26, 2007 at 09:14:00PM +1000, Nigel Cunningham wrote:
> >
> > You have the cryptd Kconfig option in (at least in rc3) - presumably
> > Maximillian has been too keen and turned it on before you were ready :)
> > It does make sense for
On Saturday, 26 May 2007 14:49, Maximilian Engelhardt wrote:
> On Saturday 26 May 2007, Nigel Cunningham wrote:
> > Hi.
> >
> > On Sat, 2007-05-26 at 11:28 +0200, Maximilian Engelhardt wrote:
> > > Hello,
> > >
> > > When I try software suspend on my laptop it always returns to my running
> > >
Based in part on Auke's patch.
Signed-off-by: Jan Engelhardt <[EMAIL PROTECTED]>
---
Documentation/CodingStyle | 74 +++---
1 file changed, 64 insertions(+), 10 deletions(-)
Index: linux-2.6.22-rc3/Documentation/CodingStyle
Uwe Bugla wrote:
OK, applied this one against 2.6.22-rc3, assuming a typo error by you, Andrew.
Result is: No change: non functionable b44 device!
Could you please send the following:
1. the output of lsmod from the non-functioning kernel
2. the output of dmesg from the non-functioning
On Saturday 26 May 2007 21:39:54 Uwe Bugla wrote:
> Am Samstag, 26. Mai 2007 21:19 schrieben Sie:
> > Uwe, please try the following patch:
> >
> > Index: bu3sch-wireless-dev/drivers/net/b44.c
> > ===
> > ---
Am Samstag, 26. Mai 2007 21:19 schrieben Sie:
> Uwe, please try the following patch:
>
> Index: bu3sch-wireless-dev/drivers/net/b44.c
> ===
> --- bu3sch-wireless-dev.orig/drivers/net/b44.c2007-05-18
> 18:09:50.0 +0200
Am Samstag, 26. Mai 2007 20:19 schrieben Sie:
> On Sat, 26 May 2007 20:03:17 +0200 Michael Buesch <[EMAIL PROTECTED]> wrote:
> > Ok, please take git and get my development tree and try with that:
> >
> > git clone http://bu3sch.de/git/wireless-dev.git
> >
> > It's based on 2.6.22-rc1 and it works
Grant Grundler wrote:
> On Sat, May 26, 2007 at 07:03:12PM +0400, Manu Abraham wrote:
>> Roland Dreier wrote:
>>> > I am now wondering whether the usage of MSI would help in this case and
>>> > that i should be using enable_msi before request_irq ?
>>>
>>> MSI interrupts are never shared. So if
On May 25 2007 10:25, Auke Kok wrote:
>diff --git a/Documentation/CodingStyle b/Documentation/CodingStyle
>index f518395..3635b38 100644
>--- a/Documentation/CodingStyle
>+++ b/Documentation/CodingStyle
>@@ -393,7 +393,7 @@ int fun(int a)
> int result = 0;
> char *buffer =
Uwe, please try the following patch:
Index: bu3sch-wireless-dev/drivers/net/b44.c
===
--- bu3sch-wireless-dev.orig/drivers/net/b44.c 2007-05-18 18:09:50.0
+0200
+++ bu3sch-wireless-dev/drivers/net/b44.c 2007-05-26
On Saturday 26 May 2007 20:58:37 Uwe Bugla wrote:
> Am Samstag, 26. Mai 2007 20:41 schrieben Sie:
> > On 5/26/07, Michael Buesch <[EMAIL PROTECTED]> wrote:
> > > On Saturday 26 May 2007 19:04:04 Uwe Bugla wrote:
> > > > Yes, sure! But the help text is very unlucky and humble, and it is not
> > > >
btw - does in-kernel lzo scale on SMP systems ?
is it a matter of lzo builtin compression or a matter of the component using
in-kernel lzo compression ?
if i write/read data on reiser4 filesystem with lzo compression on - will
all CPUs being used ?
just curious here, because i remember
Le jeudi 17 mai 2007 à 18:59 +0200, Nicolas Mailhot a écrit :
> Le jeudi 17 mai 2007 à 09:45 -0700, Randy Dunlap a écrit :
>
> > Can you boot with "kstack=32" so that we can see more of the stack?
>
> I can try. It's not triggering quickly though
Seems I was completely wrong about the trigger,
On Saturday 26 May 2007 18:13:09 Andrew Morton wrote:
> > I ask to try wireless-dev, as the driver works perfectly fine
> > for me there, but he refuses to try it, too. So I'm stuck.
>
> I don't think he knows how to obtain it.
>
> Uwe, http://userweb.kernel.org/~akpm/git-wireless.patch.gz is
Am Samstag, 26. Mai 2007 20:41 schrieben Sie:
> On 5/26/07, Michael Buesch <[EMAIL PROTECTED]> wrote:
> > On Saturday 26 May 2007 19:04:04 Uwe Bugla wrote:
> > > Yes, sure! But the help text is very unlucky and humble, and it is not
> > > clear enough in the sense of being distinctive enough, just
On Saturday 26 May 2007 20:41:09 Benoit Boissinot wrote:
> On 5/26/07, Michael Buesch <[EMAIL PROTECTED]> wrote:
> > On Saturday 26 May 2007 19:04:04 Uwe Bugla wrote:
> > > Yes, sure! But the help text is very unlucky and humble, and it is not
> > > clear
> > > enough in the sense of being
On Sat, 26 May 2007, Kyle Moffett wrote:
> AppArmor). On the other hand, if you actually want to protect the _data_,
> then tagging the _name_ is flawed; tag the *DATA* instead.
Bingo.
(This is how traditional Unix DAC has always functioned, and is what
SELinux does: object labeling).
-
On Fri, 25 May 2007, Crispin Cowan wrote:
> Finally, AA doesn't care what the contents of the executable are. We
> assume that it is a copy of metasploit or something, and confine it to
> access only the resources that the policy says.
As long as these resources are only files. There is no
On 5/26/07, Michael Buesch <[EMAIL PROTECTED]> wrote:
On Saturday 26 May 2007 19:04:04 Uwe Bugla wrote:
> Yes, sure! But the help text is very unlucky and humble, and it is not clear
> enough in the sense of being distinctive enough, just clear and
> comprehensive.
Why don't you simply submit a
On Sat, May 26, 2007 at 07:03:12PM +0400, Manu Abraham wrote:
> Roland Dreier wrote:
> > > I am now wondering whether the usage of MSI would help in this case and
> > > that i should be using enable_msi before request_irq ?
> >
> > MSI interrupts are never shared. So if pci_enable_msi()
1 - 100 of 436 matches
Mail list logo
