* Paul E. McKenney <[EMAIL PROTECTED]> wrote:
> OK, the attached instead revalidates that the task struct still
> references the sighand_struct after obtaining the lock (and passes
> kernbench and LTP, which tells me I need to get better tests!).
i've applied this to the -RT tree, and it's
On Mon, Aug 15, 2005 at 12:37:50PM -0400, Bill Jordan wrote:
> On 8/11/05, Gleb Natapov <[EMAIL PROTECTED]> wrote:
> > What about the idea that was floating around about new VM flag that will
> > instruct kernel to copy pages belonging to the vma on fork instead of mark
> > them as cow?
> >
>
>
* [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
> This patch set is based on 2.6.13-rc6 -mm1 broken out series. It applies
> and builds i386, x86_64, and um-i386 on 2.6.13-rc5. I've tested PAE and
> non-PAE SMP kernels and am working on an LDT test suite. Depends on
> the i386 cleanups, sub-arch
On Tue, Aug 16, 2005 at 09:24:25AM +1000, Dave Airlie wrote:
> > > I'm a little surprised, as a ppc64 fix theoretically shouldn't matter for
> > > x86_64? But perhaps they share something?
> >
> > My guess is that it is maybe the DRM changes that have done it... the
> > 32/64-bit code in
Patch looks good to me now. Thanks.
-Andi
-
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/
On Tue, 16 Aug 2005 01:10:23 CDT, Michael E Brown said:
> Ok, very nice. Finally some actual code review, thanks. :-)
I have to admit I'm not qualified to do a detailed review, but I try.. ;)
> These are all just standard CMOS port numbers that pretty much every
> chipset uses to access CMOS.
* [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
> Virtualization aware Linux kernels may need to redefine functions which write
> to hardware page tables at the sub-architecture layer. Previously, this was
> done by encapsulation in a split mach-xxx/pgtable-{2|3}level-ops.h file, but
> having 8
On Mon, 2005-08-15 at 16:39 -0700, George Anzinger wrote:
> I haven't looked at this new code all that closely as yet. One thing I
> did notice is that there is an assumption that the "timer being
> delivered flag" can be shared between LR timers and HR timers. I
> suspect this is wrong as
On Mon, Aug 15, 2005 at 03:05:22PM -0500, Doug Warzecha wrote:
> This patch adds the Dell Systems Management Base Driver with sysfs support.
>
> This driver has been tested with Dell OpenManage.
Much better, but I still have a few questions:
> +System Management Interrupt
> +
> +On some Dell
* Zachary Amsden ([EMAIL PROTECTED]) wrote:
> Chris Wright wrote:
> >>@@ -30,7 +33,7 @@
> >>static inline unsigned long get_desc_base(struct desc_struct *desc)
> >>{
> >>unsigned long base;
> >>- base = ((desc->a >> 16) & 0x) |
> >>+ base = (desc->a >> 16) |
> >
> >Seemingly
On Tue, 2005-08-16 at 01:36 -0400, [EMAIL PROTECTED] wrote:
> On Mon, 15 Aug 2005 23:58:43 CDT, Michael E Brown said:
>
> > No, this is an _EXCELLENT_ reason why _LESS_ of this should be in the
> > kernel. Why should we have to duplicate a _TON_ of code inside the
> > kernel to figure out which
Hi All,
> >This patch sets the WDT_ENABLE bit of the Lock Register to enable the
> >watchdog and WDT_LOCK bit only if nowayout is set. The old code always
> >sets the WDT_LOCK bit of watchdog timer for Intel 6300ESB chipset. So, we
> >end up locking the watchdog instead of enabling it.
> >
>
On Mon, Aug 15, 2005 at 10:10:28PM -0500, Michael E Brown wrote:
> On Mon, 2005-08-15 at 21:29 -0400, Kyle Moffett wrote:
> > On Aug 15, 2005, at 18:58:56, [EMAIL PROTECTED] wrote:
> > >> Why can't you just implement the system management actions in
> > >> the kernel driver? This is tantamount to
On Mon, Aug 15, 2005 at 10:10:28PM -0500, Michael E Brown wrote:
On Mon, 2005-08-15 at 21:29 -0400, Kyle Moffett wrote:
On Aug 15, 2005, at 18:58:56, [EMAIL PROTECTED] wrote:
Why can't you just implement the system management actions in
the kernel driver? This is tantamount to a binary
Hi All,
This patch sets the WDT_ENABLE bit of the Lock Register to enable the
watchdog and WDT_LOCK bit only if nowayout is set. The old code always
sets the WDT_LOCK bit of watchdog timer for Intel 6300ESB chipset. So, we
end up locking the watchdog instead of enabling it.
Signed-off-by:
On Tue, 2005-08-16 at 01:36 -0400, [EMAIL PROTECTED] wrote:
On Mon, 15 Aug 2005 23:58:43 CDT, Michael E Brown said:
No, this is an _EXCELLENT_ reason why _LESS_ of this should be in the
kernel. Why should we have to duplicate a _TON_ of code inside the
kernel to figure out which platform
* Zachary Amsden ([EMAIL PROTECTED]) wrote:
Chris Wright wrote:
@@ -30,7 +33,7 @@
static inline unsigned long get_desc_base(struct desc_struct *desc)
{
unsigned long base;
- base = ((desc-a 16) 0x) |
+ base = (desc-a 16) |
Seemingly unrelated.
Yes, alas my bucket
On Mon, Aug 15, 2005 at 03:05:22PM -0500, Doug Warzecha wrote:
This patch adds the Dell Systems Management Base Driver with sysfs support.
This driver has been tested with Dell OpenManage.
Much better, but I still have a few questions:
+System Management Interrupt
+
+On some Dell systems,
On Mon, 2005-08-15 at 16:39 -0700, George Anzinger wrote:
I haven't looked at this new code all that closely as yet. One thing I
did notice is that there is an assumption that the timer being
delivered flag can be shared between LR timers and HR timers. I
suspect this is wrong as the
* [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
Virtualization aware Linux kernels may need to redefine functions which write
to hardware page tables at the sub-architecture layer. Previously, this was
done by encapsulation in a split mach-xxx/pgtable-{2|3}level-ops.h file, but
having 8
On Tue, 16 Aug 2005 01:10:23 CDT, Michael E Brown said:
Ok, very nice. Finally some actual code review, thanks. :-)
I have to admit I'm not qualified to do a detailed review, but I try.. ;)
These are all just standard CMOS port numbers that pretty much every
chipset uses to access CMOS.
The
Patch looks good to me now. Thanks.
-Andi
-
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/
On Tue, Aug 16, 2005 at 09:24:25AM +1000, Dave Airlie wrote:
I'm a little surprised, as a ppc64 fix theoretically shouldn't matter for
x86_64? But perhaps they share something?
My guess is that it is maybe the DRM changes that have done it... the
32/64-bit code in 2.6.13-rc6 may have
* [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
This patch set is based on 2.6.13-rc6 -mm1 broken out series. It applies
and builds i386, x86_64, and um-i386 on 2.6.13-rc5. I've tested PAE and
non-PAE SMP kernels and am working on an LDT test suite. Depends on
the i386 cleanups, sub-arch
On Mon, Aug 15, 2005 at 12:37:50PM -0400, Bill Jordan wrote:
On 8/11/05, Gleb Natapov [EMAIL PROTECTED] wrote:
What about the idea that was floating around about new VM flag that will
instruct kernel to copy pages belonging to the vma on fork instead of mark
them as cow?
I think the
* Paul E. McKenney [EMAIL PROTECTED] wrote:
OK, the attached instead revalidates that the task struct still
references the sighand_struct after obtaining the lock (and passes
kernbench and LTP, which tells me I need to get better tests!).
i've applied this to the -RT tree, and it's looking
After upgrading the kernel from 2.6.10-ac8 to 2.6.12.5 the initramfs was no
longer able to mount rootfs.
mount: error 6 mounting ext3
All the configuration options are identical, and upgrading lvm2 package:
lvm2-2.00.25-1.01 - lvm2-2.01.14-1.0
device-mapper-1.00.19-2 -
On Mon, Aug 15, 2005 at 10:10:28PM -0500, Michael E Brown wrote:
To take a concrete example, I suggested to Doug to mention fan status. I
get the feeling that you possibly think that this would be better
integrated into lmsensors, or something like that.
Yes it should. That way you get the
Joe Peterson wrote:
Dave Neuer wrote:
On 8/15/05, Joe Peterson [EMAIL PROTECTED] wrote:
So, overall, I agree that we should not invent hacks to make up for
another software package's problems...
but also wrote:
If the kernel could handle that aspect, it would make all
On Tuesday 16 August 2005 00:18, john stultz wrote:
On Thu, 2005-08-04 at 17:23 +0200, Borislav Petkov wrote:
I get it. Actually, I wasn't very sure whether this is the right solution
since my desktop machine uses tsc timer as default while the laptop the
pmtmr. I also remember that there
Linus Torvalds wrote:
On Tue, 16 Aug 2005, Helge Hafting wrote:
This was interesting. At first, lots of kernels just kept working,
I almost suspected I was doing something wrong. Then the second last kernel
recompiled a lot of DRM stuff - and the crash came back!
The kernel after that
i've released the 2.6.13-rc6-rt1 tree, which can be downloaded from the
usual place:
http://redhat.com/~mingo/realtime-preempt/
as the name already suggests, i've switched to a new, simplified naming
scheme, which follows the usual naming convention of trees tracking the
mainline kernel.
Bolke de Bruin wrote:
Rolf Eike Beer wrote:
If I can still help you then depends on
your scheduling of this job. I'll try to do some hacking at the weekends.
Does this mean you will not have time until October 5th or just time in
the weekend until that time?
For the moment my weekends are more
Hello,
here is an oops I got during boot with kernel 2.6.12.4 or .5. Using debian
kernel 2.6.8 it's ok. (Dmesg from 2.6.8 kernel is attached)
PCI: Probing PCI hardware
PCI: Probing PCI hardware (bus 00)
PCI: Ignoring BAR0-3 of IDE controller :00:1f.1
PCI: Transparent bridge - :00:1e.0
cpqfcTS_reset() is never referenced from anywhere. By using the nonexistent
constant SCSI_RESET_ERROR it causes just another unneeded compile error.
Signed-off-by: Rolf Eike Beer [EMAIL PROTECTED]
--- a/drivers/scsi/cpqfcTSinit.c2005-08-13 09:34:20.0 +0200
+++
Remove compat code for Linux 2.4 and earlier.
Signed-off-by: Rolf Eike Beer [EMAIL PROTECTED]
--- a/drivers/scsi/cpqfcTScontrol.c 2005-08-13 19:00:35.0 +0200
+++ b/drivers/scsi/cpqfcTScontrol.c 2005-08-14 11:02:09.0 +0200
@@ -28,8 +28,6 @@
Hewlitt Packard Manual Part
Remove ioctls to get PCI information and driver version. These information
can be found via lspci or dmesg. Also remove two typedefs already commented
out.
Signed-off-by: Rolf Eike Beer [EMAIL PROTECTED]
--- a/drivers/scsi/cpqfcTSioctl.h 2005-08-07 20:18:56.0 +0200
+++
More whitespace cleanups:
-remove trailing whitespace
-remove brakets around return statements
-remove some double (or more) newlines
Signed-off-by: Rolf Eike Beer [EMAIL PROTECTED]
--- a/drivers/scsi/cpqfcTSi2c.c 2005-08-07 20:18:56.0 +0200
+++ b/drivers/scsi/cpqfcTSi2c.c 2005-08-14
On Tue, Aug 16, 2005 at 11:11:06AM +0200, Rolf Eike Beer wrote:
cpqfcTS_reset() is never referenced from anywhere. By using the nonexistent
constant SCSI_RESET_ERROR it causes just another unneeded compile error.
That was the old reset handler. Do you actually have this hardware?
The driver
cpqfcTSinit has a static array of PCI device and vendor ids supported by the
driver. Sounds familiar, doesn't it? Use pci_device_id as type for the
entries of this array and declare the array as MODULE_DEVICE_TABLE. Also use
pci_get_device() instead of pci_find_device() and remove some
Hi,
On Marcelo's request I have taken a closer look at this.
It seems that Alexander Pytlev's original (simple) patch was correct.
Without it the logic looks a bit like this.
while (...) {
if iocharset
...
else if map
...
if session
Hi,
this is a followup for the patch I sent earlier (like about 2 minutes
ago) regarding isofs options parsing. In the course of debuging this
Marcelo pointed out the following code
#ifdef CONFIG_JOLIET
if (!strcmp(this_char,iocharset) value) {
Christoph Hellwig wrote:
On Tue, Aug 16, 2005 at 11:11:06AM +0200, Rolf Eike Beer wrote:
cpqfcTS_reset() is never referenced from anywhere. By using the
nonexistent constant SCSI_RESET_ERROR it causes just another unneeded
compile error.
That was the old reset handler. Do you actually have
i have released the 2.6.13-rc6-rt2 tree, which can be downloaded from
the usual place:
http://redhat.com/~mingo/realtime-preempt/
it includes a single bugfix, which fixes a HRT timer-latency problem,
and which could explain some of the crashes/reboots Thomas Gleixner was
seeing on his
Thats great for the perl6 people.
http://dev.perl.org/perl6/doc/design/syn/S03.html says they are going
to be using « and » as operators...
Is Larry smoking crack? That's one of the worst ideas I've heard in a
long time. There's no easy way to enter those at the keyboard!
I have
Hi!
It is sometimes useful to know device access time. Things that I have in
mind are the software-based hard disk inactivity spindown (some brain
damaged IDE drives fail to follow hdparm -S if the argument is longer
than 1/2 hour) and sound card muting if it is not touched for a while.
Hello,
HRT are really very cool, but my test program indicates a bug:
4612304528077750272
4612304528077750272
4612304528077750272
4612304528077750272
4612304528077750272
...
When CLOCK_MONOTONIC_HR is changed to CLOCK_MONOTONIC
the numbers are OK. Problem is with clock_gettime (I haven't tried
With 2.6.13-rc6-git5 I started getting the below errors. Despite of the
errors everything works fine. (only problem is that I have to
disconnect /reconnect the usb mouse for it to get detected..)
[ 47.883970] PCI: Failed to allocate mem resource #10:[EMAIL PROTECTED]
for 000 0:02:04.0
[
Hi all,
While doing insmod for a psuedo driver, kernel is dumping a stack because
sleep function is called.
My init_module function for psuedo driver calls add_disk to register admin
device.
In add_disk(), kernel is allocating memory using kmalloc with flag
GFP_KERNEL. This is hardcoded in kernel
On Tue, 2005-08-16 at 15:37 +0530, shahid shaikh wrote:
Hi all,
While doing insmod for a psuedo driver, kernel is dumping a stack because
sleep function is called.
My init_module function for psuedo driver calls add_disk to register admin
device.
In add_disk(), kernel is allocating memory
Installed stock 2.6.12.3 on a brand new amd64 box with an Asus extreme
AX 300 SE/t mainboard.
I remember seeing a message in the boot saying something along:
cannot connect to hardware clock.
And now I see that the time is changing too fast (about 2 seconds each second).
I don't have visual
What's AS UP1 in your subject?
On Tue, Aug 16, 2005 at 03:37:07PM +0530, shahid shaikh wrote:
Hi all,
While doing insmod for a psuedo driver, kernel is dumping a stack because
sleep function is called.
My init_module function for psuedo driver calls add_disk to register admin
device.
In
Hi,
On 8/15/05, Bjorn Helgaas [EMAIL PROTECTED] wrote:
On Friday 12 August 2005 2:40 am, Alan Cox wrote:
Assuming all IA-64 boxes are PCI or better then you actually want to
edit include/asm-ia64/ide.h and edit ide_default_io_base where someone
years ago cut and pasted x86-32 values so
On 8/16/05, Bartlomiej Zolnierkiewicz [EMAIL PROTECTED] wrote:
Hi,
On 8/15/05, Bjorn Helgaas [EMAIL PROTECTED] wrote:
On Friday 12 August 2005 2:40 am, Alan Cox wrote:
Assuming all IA-64 boxes are PCI or better then you actually want to
edit include/asm-ia64/ide.h and edit
On 8/11/05, Christoph Hellwig [EMAIL PROTECTED] wrote:
On Thu, Aug 11, 2005 at 02:24:43PM -0600, Bjorn Helgaas wrote:
IA64 boxes only have PCI IDE devices, so there's no need to blindly poke
around in I/O port space. Poking at things that don't exist causes MCAs
on HP ia64 systems.
From: Arjan van de Ven [EMAIL PROTECTED]
My code does nothing do it.
I need a volunteer to implement it.
it's actually not too hard; all you need is to use SSE and not MMX; and
then just store sse register you're overwriting on the stack or so...
oh, really? Does the linux kernel take
Hi
My code does nothing do it.
I need a volunteer to implement it.
it's actually not too hard; all you need is to use SSE and not MMX; and
then just store sse register you're overwriting on the stack or so...
oh, really? Does the linux kernel take care of
SSE save/restore on
On Tue, 2005-08-16 at 19:16 +0900, Hiro Yoshioka wrote:
From: Arjan van de Ven [EMAIL PROTECTED]
My code does nothing do it.
I need a volunteer to implement it.
it's actually not too hard; all you need is to use SSE and not MMX; and
then just store sse register you're overwriting
Daniel Phillips [EMAIL PROTECTED] wrote:
I want to know when a page is going to be modified so that I
can predict the state of the cache as much as possible. I don't want
userspace processes corrupting the cache in unrecorded ways.
There are two cases:
1) Metadata. If anybody is
Hi,
My code does nothing do it.
I need a volunteer to implement it.
it's actually not too hard; all you need is to use SSE and not MMX; and
then just store sse register you're overwriting on the stack or so...
oh, really? Does the linux kernel take care of
SSE
Jeff:
The attached file is the incremental patch to the original uli526x.c I send
you first time,
I modify the source according to your advice, thanks.
Signed-off-by: Peer Chen [EMAIL PROTECTED]
(See attached file: patch_uli526x_inc)
Best Regards
Peer
|-+---
|
Nfsd uses it to serve up nfs exports that don't cross mountpoints (or do, if
crossmnt is specified in /etc/exports.
Is not this called nohide?
Jan Engelhardt
--
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
Hi!
This fixes debugging in soc_common.c (vprintk, not printk may be used
at that point), makes no cpufreq hooks a little bit safer and fixes
whitespace a tiny bit. Please apply,
Pavel
diff --git a/drivers/pcmcia/soc_common.c
Hi!
The PowerOP infrastructure you suggest surely is one path to better runtime
power management in the Linux kernel. However, I don't like it at all in its
current implementation. Here are a few suggestions for improvements,
rewrites, and so on:
First, the table interface you suggest is ugly.
A small add-on:
We need to make sure that we're capable of handling smart CPUs like Transmeta
Crusoe processors in a sane way. This means
b)Setting of values
is optional if the hardware itself can be set to a min/max value (step a
above in previous mail).
Dominik
-
To unsubscribe
Hello Dave,
after suspend-to-ram and a subsequent resume the configuration
of my AGP bridge/controller is different and X will refuse to
start after resume if it wasn't running during suspend. I'm
using radeonfb as console driver and kernel 2.6.13-rc6-git6.
Diff between lspci -vvvxxx before and
i get this error during compile of pci drivers:
CC drivers/pci/access.o
CC drivers/pci/bus.o
CC drivers/pci/probe.o
CC drivers/pci/remove.o
CC drivers/pci/pci.o
CC drivers/pci/quirks.o
drivers/pci/quirks.c: In function ‘quirk_via_irq’:
Paul E. McKenney wrote:
OK, the attached instead revalidates that the task struct still references
the sighand_struct after obtaining the lock
Personally I think this is a way to go. A nitpick suggestion,
could you make a separate function (say, lock_task_sighand)
which does all this job?
mardi 16 Août 2005 13:41, Mr Machine wrote/a écrit :
i get this error during compile of pci drivers:
CC drivers/pci/access.o
CC drivers/pci/bus.o
CC drivers/pci/probe.o
CC drivers/pci/remove.o
CC drivers/pci/pci.o
CC drivers/pci/quirks.o
Hi Nathan,
if (driver-flags I2C_DF_NOTIFY) {
list_for_each(item,adapters) {
adapter = list_entry(item, struct i2c_adapter, list);
- driver-attach_adapter(adapter);
+ if (driver-attach_adapter)
+
On 228, 08 16, 2005 at 01:36:19AM -0400, [EMAIL PROTECTED] wrote:
On Mon, 15 Aug 2005 23:58:43 CDT, Michael E Brown said:
No, this is an _EXCELLENT_ reason why _LESS_ of this should be in the
kernel. Why should we have to duplicate a _TON_ of code inside the
kernel to figure out which
i have released the 2.6.13-rc6-rt3 tree, which can be downloaded from
the usual place:
http://redhat.com/~mingo/realtime-preempt/
Changes since 2.6.13-rc6-rt2:
- reverted an incorrect tasklist_lock - lock_task() conversion that
slipped in via an earlier hack in the HRT code. The issue
* Mr Machine [EMAIL PROTECTED] wrote:
i get this error during compile of pci drivers:
if this helps, here's the realtime configuration section from my
.config file:
could you send me the full .config file? That's the easiest way for me
to reproduce your build problem.
Ingo
-
To
linux-kernel@vger.kernel.org 16.08.2005
OCPPXXMPTMIYRYJRONKSJBYMIPRJRKFGPJIRWH
attachment: R587DK324V.jpg
Do you see grub saying uncompressing kernel... or whatever that says?
Grub says...
root (hd2,2)
Filesystem type is ext2fs, partition type 0x83
kernel /boot/vmlinuz-2.6.12.4 root=/dev/md0 ro nodma
[Linux-bzImage, setup=0x1e00, size=0x1302ff]
May I suggest to try a boot with Gujin
On Maw, 2005-08-16 at 11:38 +0200, Bartlomiej Zolnierkiewicz wrote:
* removing IDE_ARCH_OBSOLETE_INIT define has some implications,
* non-functional ide-cs driver (but there is no PCMCIA on IA64?)
IA64 systems can support PCI-Cardbus/PCMCIA cards so they do actually
need this support. They
Ingo Molnar wrote:
i've released the 2.6.13-rc6-rt1 tree, which can be downloaded from the
usual place:
http://redhat.com/~mingo/realtime-preempt/
as the name already suggests, i've switched to a new, simplified naming
scheme, which follows the usual naming convention of trees tracking the
Hi,
it seems that PCI quirks are not handled on resume which results
in all kinds of strange effects, like disappeared PCI devices.
Below is a diff between lspci -vvvxxx before and after resume
for my SMBus device which only gets enabled by PCI quirk handling.
-:00:1f.3 SMBus: Intel Corp.
* Serge Noiraud [EMAIL PROTECTED] wrote:
mardi 16 Août 2005 13:41, Mr Machine wrote/a écrit :
i get this error during compile of pci drivers:
I have the same problem with rt1 and rt2.
i have fixed this in -rt4 (just uploaded).
One 'bizarre' thing : If I patch directly 2.6.13.rc6 with the
Hi,
On 8/16/05, Peter Williams [EMAIL PROTECTED] wrote:
Peter Williams wrote:
Michal Piotrowski wrote:
Hi,
here are my benchmarks (part1):
Would you mind doing a few extra runs when you do Zaphod with different
configuration parameters? Namely:
1. default value for
Arjan van de Ven [EMAIL PROTECTED] writes:
not on kernel entry afaik.
However just save the register on the stack and put it back at the
end...
You need to do more than that, like disabling lazy FPU mode.
That is what kernel_fpu_begin/end takes care of.
However it disables preemption,
A read() on a TCP/IP socket, which should block returns -1 with errno=EAGAIN
Unless I am mistaken, the read() should block as the socket is active with no
problems. The only unusual items are that I have set the network buffer
size to 32K (32 * 1024), IPTOS_THROUGHPUT, and keepalive. In
Rolf Eike Beer napsal(a):
Signed-off-by: Rolf Eike Beer [EMAIL PROTECTED]
--- a/drivers/scsi/cpqfcTSinit.c2005-08-14 14:20:40.0 +0200
+++ b/drivers/scsi/cpqfcTSinit.c2005-08-14 14:25:33.0 +0200
@@ -264,18 +264,14 @@ static void launch_FCworker_thread(struc
*
On Tue, Aug 16, 2005 at 02:30:51AM +1000, Con Kolivas wrote:
Time definitely was lost the longer the machine was running.
I think I found the reason for time drift. Basically cur_timer-mark_offset
doesnt expect to be called from non-timer interrupt handler. Hence it drops
one jiffy from the lost
On Tue, 16 Aug 2005 23:19, Srivatsa Vaddagiri wrote:
On Tue, Aug 16, 2005 at 02:30:51AM +1000, Con Kolivas wrote:
Time definitely was lost the longer the machine was running.
I think I found the reason for time drift. Basically cur_timer-mark_offset
doesnt expect to be called from non-timer
On Tue, 2005-08-16 at 01:16 -0700, Greg KH wrote:
On Mon, Aug 15, 2005 at 10:10:28PM -0500, Michael E Brown wrote:
To take a concrete example, I suggested to Doug to mention fan status. I
get the feeling that you possibly think that this would be better
integrated into lmsensors, or
Thanks a lot Willy,
I try to find something in this way...
Note, that i test my board with an image with Kernel 2.4 and work well.. but
it's a no-free version (i don't have source or configuration) ... Me, i want to
boot with my own kernel and find correct configuration...
This system use, i
Dear Lenneart,
Good Morning. Sorry for the delay.
It is Independence Day celebration Week in INDIA. And it's time for my
independence from this problem.
Please see my advances in-lined below.
Work time
---
And is it due to lack of partition support in the driver that will
affect the
Dear Lennart,
I have bought a entermultimedia USB 2.0 21-in-1 card.
There are no Linux driver support in the CD provided.
Can u suggest me what is best bug (USB card reader) with Linux driver
support in the Market.
Regards,
Mukund Jampala
-Original Message-
From: Lennart Sorensen
On Maw, 2005-08-16 at 15:19 +0200, Kern Sibbald wrote:
have written, nor does it write() anything. When my read() is issued, I
expect it to block, but it immediately returns with -1 and errno set to
EAGAIN. If the read() is re-issued, a CPU intensive loop results as long as
the other end
On Sun, Aug 14, 2005 at 08:00:31PM +, Lee Revell wrote:
We write code in ASCII, dammit.
URL: http://www.madore.org/~david/weblog/2004-12.html#d.2004-12-03.0813
:-)
--
David A. Madore
([EMAIL PROTECTED],
http://www.madore.org/~david/ )
-
To unsubscribe from
On Tue, Aug 16, 2005 at 07:04:34PM +0530, Mukund JB. wrote:
Dear Lennart,
I have bought a entermultimedia USB 2.0 21-in-1 card.
There are no Linux driver support in the CD provided.
Can u suggest me what is best bug (USB card reader) with Linux driver
support in the Market.
It doesn't
Hi!
You also achieved some sort of new low point in the abuse of StudlyCaps
there. Please, let's not get started on mixed case acronyms.
My patch has been around for quite a while, and no-one else has complained,
not even you before this point. Plus, you don't seem to be complaining
On 08/15/05 20:52, [EMAIL PROTECTED] wrote:
Actually, I view this as being a little odd...
What is :00:04:0 in this case ? The device is not a serial
port, which is what the ttyXX back link would lead you to believe.
Thus, it's a serial port multiplexer that supports up to N ports,
On 08/15/05 21:08, James Bottomley wrote:
Think if SCSI used this same style of representation. For example,
if there was no scsi target device entity, but class entities did
exist and they just pointed back to the scsi host device entry.
Yes, it's theoretically possible to have had SCSI do
Jiri Slaby wrote:
Rolf Eike Beer napsal(a):
Signed-off-by: Rolf Eike Beer [EMAIL PROTECTED]
--- a/drivers/scsi/cpqfcTSinit.c 2005-08-14 14:20:40.0 +0200
+++ b/drivers/scsi/cpqfcTSinit.c 2005-08-14 14:25:33.0 +0200
@@ -264,18 +264,14 @@ static void
On Tuesday 16 August 2005 16:03, Alan Cox wrote:
On Maw, 2005-08-16 at 15:19 +0200, Kern Sibbald wrote:
have written, nor does it write() anything. When my read() is issued, I
expect it to block, but it immediately returns with -1 and errno set to
EAGAIN. If the read() is re-issued, a CPU
interface.
+ * 20050610 henk Cleanups, make it ready for public consumption.
+ * 20050630 henk Cleanups, fixes in response to comments.
+ * 20050701 henk sysfs write serialisation, fix potential unload races
+ * 20050801 henk Added ringtone, restructure USB
+ * 20050816 henk
On Maw, 2005-08-16 at 16:12 +0200, Kern Sibbald wrote:
I verified that I have not explicitly set nonblocking on the socket, so
expect
it to be default blocking.
Depends where it came from and what OS. In particular the blocking state
of a socket returned from accept may be the same as the
On Tue, 16 Aug 2005, Ingo Molnar wrote:
* Peter Zijlstra [EMAIL PROTECTED] wrote:
--- linux-2.6.13-rc6-git7-RT-V0.7.53-11/drivers/usb/core/hcd.c~ 2005-08-15
21:23:45.0 +0200
+++ linux-2.6.13-rc6-git7-RT-V0.7.53-11/drivers/usb/core/hcd.c 2005-08-15
22:03:33.0 +0200
301 - 400 of 626 matches
Mail list logo
