[PATCH 0/1] xhci: Recognize USB 3.0 devices as superspeed at powerup

2012-08-22 Thread manoj . iyer
From: Manoj Iyer On Intel Panther Point chipset USB 3.0 devices show up as high-speed devices on powerup, but after an s3 cycle they are correctly recognized as SuperSpeed. At powerup switch the port to xHCI so that USB 3.0 devices are correctly recognized. This is a second attempt at fixing

Re: [PATCH 1/1] xhci: Unconditionally switch ports to xHCI on powerup

2012-08-22 Thread Manoj Iyer
will send out a new seperate patch with the fix. Thanks Manoj Thanks, Andiry On Tue, 21 Aug 2012, Andiry Xu wrote: On Tue, Aug 21, 2012 at 12:06 PM, wrote: From: Manoj Iyer USB 3.0 devices show up as high-speed devices on powerup, after an s3 cycle they are correctly recognized

Re: [PATCH 1/1] xhci: Unconditionally switch ports to xHCI on powerup

2012-08-22 Thread Manoj Iyer
will send out a new seperate patch with the fix. Thanks Manoj Thanks, Andiry On Tue, 21 Aug 2012, Andiry Xu wrote: On Tue, Aug 21, 2012 at 12:06 PM, manoj.i...@canonical.com wrote: From: Manoj Iyer manoj.i...@canonical.com USB 3.0 devices show up as high-speed devices on powerup

[PATCH 0/1] xhci: Recognize USB 3.0 devices as superspeed at powerup

2012-08-22 Thread manoj . iyer
From: Manoj Iyer manoj.i...@canonical.com On Intel Panther Point chipset USB 3.0 devices show up as high-speed devices on powerup, but after an s3 cycle they are correctly recognized as SuperSpeed. At powerup switch the port to xHCI so that USB 3.0 devices are correctly recognized

[PATCH 1/1] xhci: Recognize USB 3.0 devices as superspeed at powerup

2012-08-22 Thread manoj . iyer
From: Manoj Iyer manoj.i...@canonical.com On Intel Panther Point chipset USB 3.0 devices show up as high-speed devices on powerup, but after an s3 cycle they are correctly recognized as SuperSpeed. At powerup switch the port to xHCI so that USB 3.0 devices are correctly recognized. BugLink: http

Re: [PATCH 1/1] xhci: Unconditionally switch ports to xHCI on powerup

2012-08-21 Thread Manoj Iyer
as well. On Tue, 21 Aug 2012, Andiry Xu wrote: On Tue, Aug 21, 2012 at 12:06 PM, wrote: From: Manoj Iyer USB 3.0 devices show up as high-speed devices on powerup, after an s3 cycle they are correctly recognized as SuperSpeed. At powerup unconditionally switch the port to xHCI like we do when

Re: [PATCH 1/1] xhci: Unconditionally switch ports to xHCI on powerup

2012-08-21 Thread Manoj Iyer
as well. On Tue, 21 Aug 2012, Andiry Xu wrote: On Tue, Aug 21, 2012 at 12:06 PM, manoj.i...@canonical.com wrote: From: Manoj Iyer manoj.i...@canonical.com USB 3.0 devices show up as high-speed devices on powerup, after an s3 cycle they are correctly recognized as SuperSpeed. At powerup

[PATCH 1/1] xhci: Unconditionally switch ports to xHCI on powerup

2012-08-20 Thread manoj . iyer
From: Manoj Iyer USB 3.0 devices show up as high-speed devices on powerup, after an s3 cycle they are correctly recognized as SuperSpeed. At powerup unconditionally switch the port to xHCI like we do when we resume from suspend. BugLink: http://bugs.launchpad.net/bugs/1000424 Signed-off

[PATCH 0/1] xhci: Unconditionally switch ports to xHCI on powerup

2012-08-20 Thread manoj . iyer
From: Manoj Iyer USB 3.0 devices show up as high-speed devices on powerup, after an s3 cycle they are correctly recognized as SuperSpeed. At powerup unconditionally switch the port to xHCI like we do when we resume from suspend. BugLink: http://bugs.launchpad.net/bugs/1000424 Test results

[PATCH 0/1] xhci: Unconditionally switch ports to xHCI on powerup

2012-08-20 Thread manoj . iyer
From: Manoj Iyer manoj.i...@canonical.com USB 3.0 devices show up as high-speed devices on powerup, after an s3 cycle they are correctly recognized as SuperSpeed. At powerup unconditionally switch the port to xHCI like we do when we resume from suspend. BugLink: http://bugs.launchpad.net/bugs

[PATCH 1/1] xhci: Unconditionally switch ports to xHCI on powerup

2012-08-20 Thread manoj . iyer
From: Manoj Iyer manoj.i...@canonical.com USB 3.0 devices show up as high-speed devices on powerup, after an s3 cycle they are correctly recognized as SuperSpeed. At powerup unconditionally switch the port to xHCI like we do when we resume from suspend. BugLink: http://bugs.launchpad.net/bugs

[PATCH] thinkpad-acpi: recognize latest V-Series using DMI_BIOS_VENDOR

2012-08-06 Thread manoj . iyer
From: Manoj Iyer In the latest V-series bios DMI_PRODUCT_VERSION does not contain the string Lenovo or Thinkpad, but is set to the model number, this causes the thinkpad_acpi module to fail to load. Recognize laptop as Lenovo using DMI_BIOS_VENDOR instead, which is set to Lenovo. Test on V490u

[PATCH] thinkpad-acpi: recognize latest V-Series using DMI_BIOS_VENDOR

2012-08-06 Thread manoj . iyer
From: Manoj Iyer In the latest V-series bios DMI_PRODUCT_VERSION does not contain the string Lenovo or Thinkpad, but is set to the model number, this causes the thinkpad_acpi module to fail to load. Recognize laptop as Lenovo using DMI_BIOS_VENDOR instead, which is set to Lenovo. Signed-off

[PATCH] thinkpad-acpi: recognize latest V-Series using DMI_BIOS_VENDOR

2012-08-06 Thread manoj . iyer
From: Manoj Iyer In the latest V-series bios DMI_PRODUCT_VERSION does not contain the string Lenovo or Thinkpad, but is set to the model number, this causes the thinkpad_acpi module to fail to load. Recognize laptop as Lenovo using DMI_BIOS_VENDOR instead, which is set to Lenovo. Signed-off

[PATCH] thinkpad-acpi: recognize latest V-Series using

2012-08-06 Thread manoj . iyer
From: Manoj Iyer Please consider this patch to thinkapd_acpi, it loads the module on V-series systems that do not report with "Lenovo" or "ThinkPad" prefix to DMI_PRODUCT_VERSION query, but only returns model name. ==

[PATCH] thinkpad-acpi: recognize latest V-Series using

2012-08-06 Thread manoj . iyer
From: Manoj Iyer manoj.i...@canonical.com Please consider this patch to thinkapd_acpi, it loads the module on V-series systems that do not report with Lenovo or ThinkPad prefix to DMI_PRODUCT_VERSION query, but only returns model name

[PATCH] thinkpad-acpi: recognize latest V-Series using DMI_BIOS_VENDOR

2012-08-06 Thread manoj . iyer
From: Manoj Iyer manoj.i...@canonical.com In the latest V-series bios DMI_PRODUCT_VERSION does not contain the string Lenovo or Thinkpad, but is set to the model number, this causes the thinkpad_acpi module to fail to load. Recognize laptop as Lenovo using DMI_BIOS_VENDOR instead, which is set

[PATCH] thinkpad-acpi: recognize latest V-Series using DMI_BIOS_VENDOR

2012-08-06 Thread manoj . iyer
From: Manoj Iyer manoj.i...@canonical.com In the latest V-series bios DMI_PRODUCT_VERSION does not contain the string Lenovo or Thinkpad, but is set to the model number, this causes the thinkpad_acpi module to fail to load. Recognize laptop as Lenovo using DMI_BIOS_VENDOR instead, which is set

[PATCH] thinkpad-acpi: recognize latest V-Series using DMI_BIOS_VENDOR

2012-08-06 Thread manoj . iyer
From: Manoj Iyer manoj.i...@canonical.com In the latest V-series bios DMI_PRODUCT_VERSION does not contain the string Lenovo or Thinkpad, but is set to the model number, this causes the thinkpad_acpi module to fail to load. Recognize laptop as Lenovo using DMI_BIOS_VENDOR instead, which is set

Re: [PATCH] thinkpad-acpi: recognize latest V-Series using DMI_BIOS_VENDOR

2012-08-02 Thread Manoj Iyer
Oops! This is embarrassing! my logic is flawed. Please ignore this patch, I will resend it NACK On Thu, 2 Aug 2012, manoj.i...@canonical.com wrote: From: Manoj Iyer In the latest V-series bios DMI_PRODUCT_VERSION does not contain the string Lenovo or Thinkpad, but is set to the model

[PATCH] thinkpad-acpi: recognize latest V-Series using DMI_BIOS_VENDOR

2012-08-02 Thread manoj . iyer
From: Manoj Iyer In the latest V-series bios DMI_PRODUCT_VERSION does not contain the string Lenovo or Thinkpad, but is set to the model number, this causes the thinkpad_acpi module to fail to load. Recognize laptop as Lenovo using DMI_BIOS_VENDOR instead, which is set to Lenovo. Signed-off

[PATCH] thinkpad-acpi: recognize latest V-Series using DMI_BIOS_VENDOR

2012-08-02 Thread manoj . iyer
From: Manoj Iyer In the latest V-series bios DMI_PRODUCT_VERSION does not contain the string Lenovo or Thinkpad, but is set to the model number, this causes the thinkpad_acpi module to fail to load. Recognize laptop as Lenovo using DMI_BIOS_VENDOR instead, which is set to Lenovo. BIOS

[PATCH] thinkpad-acpi: recognize latest V-Series using DMI_BIOS_VENDOR

2012-08-02 Thread manoj . iyer
From: Manoj Iyer manoj.i...@canonical.com In the latest V-series bios DMI_PRODUCT_VERSION does not contain the string Lenovo or Thinkpad, but is set to the model number, this causes the thinkpad_acpi module to fail to load. Recognize laptop as Lenovo using DMI_BIOS_VENDOR instead, which is set

[PATCH] thinkpad-acpi: recognize latest V-Series using DMI_BIOS_VENDOR

2012-08-02 Thread manoj . iyer
From: Manoj Iyer manoj.i...@canonical.com In the latest V-series bios DMI_PRODUCT_VERSION does not contain the string Lenovo or Thinkpad, but is set to the model number, this causes the thinkpad_acpi module to fail to load. Recognize laptop as Lenovo using DMI_BIOS_VENDOR instead, which is set

Re: [PATCH] thinkpad-acpi: recognize latest V-Series using DMI_BIOS_VENDOR

2012-08-02 Thread Manoj Iyer
Oops! This is embarrassing! my logic is flawed. Please ignore this patch, I will resend it NACK On Thu, 2 Aug 2012, manoj.i...@canonical.com wrote: From: Manoj Iyer manoj.i...@canonical.com In the latest V-series bios DMI_PRODUCT_VERSION does not contain the string Lenovo or Thinkpad

[PATCH] Bluetooth: btusb: Add vendor specific ID (0a5c:21f4) BCM20702A0

2012-07-10 Thread manoj . iyer
From: Manoj Iyer Patch adds support for BCM20702A0 device id (0a5c:21f4). usb-devices after patch was applied: T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0a5c ProdID=21f4 Rev=01.12 S: Manufacturer=Broadcom

[PATCH] Bluetooth: btusb: Add vendor specific ID (0a5c:21f4) BCM20702A0

2012-07-10 Thread manoj . iyer
From: Manoj Iyer manoj.i...@canonical.com Patch adds support for BCM20702A0 device id (0a5c:21f4). usb-devices after patch was applied: T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=0a5c ProdID=21f4 Rev=01.12 S

Re: [PATCH] Bluetooth: btusb: Add vendor specific ID (0a5c:21f4) BCM20702A0

2012-07-06 Thread Manoj Iyer
Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) I: If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none) Hi Manoj, * Manoj Iyer [2012-04-11 13:39:23 -0500]: usb-devices: T: Bus=01 Lev=02 Prnt=02 Port=03 Cnt=02 Dev#= 4

Re: [PATCH] Bluetooth: btusb: Add vendor specific ID (0a5c:21f4) BCM20702A0

2012-07-06 Thread Manoj Iyer
Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none) I: If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none) Hi Manoj, * Manoj Iyer manoj.i...@canonical.com [2012-04-11 13:39:23 -0500]: usb-devices: T: Bus=01 Lev=02 Prnt=02

Re: [ext3][kernels >= 2.6.20.7 at least] KDE going comatose when FS is under heavy write load (massive starvation)

2007-04-27 Thread Manoj Joseph
on write"! ZFS (Sun) and WAFL (NetApp) does this. Don't know about WAFL, but ZFS does logging too. -Manoj -- Manoj Joseph http://kerneljunkie.blogspot.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED

Re: [ext3][kernels >= 2.6.20.7 at least] KDE going comatose when FS is under heavy write load (massive starvation)

2007-04-27 Thread Manoj Joseph
drew Morton knew what he was doing and the consequences. But unless you care nothing about your data, you should not do it. It is as simple as that. No, it does not give you a robust desktop!! -Manoj -- Manoj Joseph http://kerneljunkie.blogspot.com/ - To unsubscribe from this list: send the l

Re: [ext3][kernels = 2.6.20.7 at least] KDE going comatose when FS is under heavy write load (massive starvation)

2007-04-27 Thread Manoj Joseph
he was doing and the consequences. But unless you care nothing about your data, you should not do it. It is as simple as that. No, it does not give you a robust desktop!! -Manoj -- Manoj Joseph http://kerneljunkie.blogspot.com/ - To unsubscribe from this list: send the line unsubscribe linux

Re: [ext3][kernels = 2.6.20.7 at least] KDE going comatose when FS is under heavy write load (massive starvation)

2007-04-27 Thread Manoj Joseph
) and WAFL (NetApp) does this. Don't know about WAFL, but ZFS does logging too. -Manoj -- Manoj Joseph http://kerneljunkie.blogspot.com/ - 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

Re: ZFS with Linux: An Open Plea

2007-04-18 Thread Manoj Joseph
to exclude Linux. I thought you said "incompatible with other OS products". I believe there are other OS products it is quite compatible with. The ports of ZFS seem to confirm this. That it is compatible with the Linux kernel was not what I was arguing. :) -Manoj - To unsubscribe from

Re: ZFS with Linux: An Open Plea

2007-04-18 Thread Manoj Joseph
. Please do see: http://www.opensolaris.org/os/about/faq/licensing_faq/#patents ZFS has been ported to some of those 'other OS products'. :) My two cents... -Manoj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More

Re: ZFS with Linux: An Open Plea

2007-04-18 Thread Manoj Joseph
. Please do see: http://www.opensolaris.org/os/about/faq/licensing_faq/#patents ZFS has been ported to some of those 'other OS products'. :) My two cents... -Manoj - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo

Re: ZFS with Linux: An Open Plea

2007-04-18 Thread Manoj Joseph
to exclude Linux. I thought you said incompatible with other OS products. I believe there are other OS products it is quite compatible with. The ports of ZFS seem to confirm this. That it is compatible with the Linux kernel was not what I was arguing. :) -Manoj - To unsubscribe from this list: send

Re: [PATCH] 2.4.31 O_DIRECT support for ext3

2005-08-10 Thread Manoj Sharma
On Tue, 9 Aug 2005, Arjan van de Ven wrote: > On Tue, 2005-08-09 at 18:35 +0530, [EMAIL PROTECTED] wrote: > > Hi, > > > > This is back-port of O_DIRECT support for ext3 from 2.6 to 2.4.31 > > kernel. > > > > Any suggestions/comments ? > > why? > > personally I think this is way out of scope for a

Re: [PATCH] 2.4.31 O_DIRECT support for ext3

2005-08-10 Thread Manoj Sharma
On Tue, 9 Aug 2005, Arjan van de Ven wrote: On Tue, 2005-08-09 at 18:35 +0530, [EMAIL PROTECTED] wrote: Hi, This is back-port of O_DIRECT support for ext3 from 2.6 to 2.4.31 kernel. Any suggestions/comments ? why? personally I think this is way out of scope for a 2.4.x release in

Problem with DCE with Kernel Patch

2005-03-09 Thread Singal, Manoj Kumar (STSD)
a similar problem and resolved it ? . Any pointers in this regard will be really *nice*. Thanks in advance. -- Manoj - 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

Problem with DCE with Kernel Patch

2005-03-09 Thread Singal, Manoj Kumar (STSD)
a similar problem and resolved it ? . Any pointers in this regard will be really *nice*. Thanks in advance. -- Manoj - 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

kernel panic with 2.4.3

2001-07-20 Thread Manoj Sharma
directly as I am not on the linux-kernel mailing list. Thanks, Manoj ([EMAIL PROTECTED]) NMI Watchdog detected LOCKUP on CPU0, registers: CPU:0 EIP:0010:[] EFLAGS: 0086 eax: ebx: cdfe4000 ecx: cdfe8db8 edx

kernel panic with 2.4.3

2001-07-20 Thread Manoj Sharma
directly as I am not on the linux-kernel mailing list. Thanks, Manoj ([EMAIL PROTECTED]) NMI Watchdog detected LOCKUP on CPU0, registers: CPU:0 EIP:0010:[c0217900] EFLAGS: 0086 eax: ebx: cdfe4000 ecx

Next hop and o/p i/f IP address

2001-06-15 Thread Manoj Sontakke
t->dev->ip_ptr->in_dev->ifa_list->ifa_address is o/p i/f ip address and skb->dst->neighbour->dev->ip_ptr->in_dev->ifa_list->ifa_address is next hop IP address Please correct me if I

Next hop and o/p i/f IP address

2001-06-15 Thread Manoj Sontakke
-in_dev-ifa_list-ifa_address is o/p i/f ip address and skb-dst-neighbour-dev-ip_ptr-in_dev-ifa_list-ifa_address is next hop IP address Please correct me if I am wrong. Thanks for all the help. Manoj

Re: which gcc version?

2001-04-05 Thread Manoj Sontakke
hi On Thu, 5 Apr 2001, Alexander Viro wrote: > On Thu, 5 Apr 2001, Manoj Sontakke wrote: > > > Hi > > I am getting linker error "undefined reference to __divdi3". > > This is because c = a/b; where a,b,c are of type "long long" > > I

Re: which gcc version?

2001-04-05 Thread Manoj Sontakke
hi On Thu, 5 Apr 2001, Alexander Viro wrote: On Thu, 5 Apr 2001, Manoj Sontakke wrote: Hi I am getting linker error "undefined reference to __divdi3". This is because c = a/b; where a,b,c are of type "long long" I understand this is gcc problem. I am doi

which gcc version?

2001-04-04 Thread Manoj Sontakke
Hi I am getting linker error "undefined reference to __divdi3". This is because c = a/b; where a,b,c are of type "long long" I understand this is gcc problem. I am doing this on a pentium with gcc -v = egcs-2.91.66 Thanks for all the help. Manoj - To unsubs

which gcc version?

2001-04-04 Thread Manoj Sontakke
Hi I am getting linker error "undefined reference to __divdi3". This is because c = a/b; where a,b,c are of type "long long" I understand this is gcc problem. I am doing this on a pentium with gcc -v = egcs-2.91.66 Thanks for all the help. Manoj - To unsubs

Re: Packet/frame generator

2001-03-30 Thread Manoj Sontakke
On Fri, 30 Mar 2001, Mircea Ciocan wrote: > Here is a nice packet building library: > > www.packetfactory.net/Projects/Libnet/ its broken. > > Can anyone tell me a good packet/frame generator for linux? > > thanks > > > > manoj - To unsubscr

Packet/frame generator

2001-03-30 Thread Manoj Sontakke
Hi Can anyone tell me a good packet/frame generator for linux? thanks manoj - 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 re

Packet/frame generator

2001-03-30 Thread Manoj Sontakke
Hi Can anyone tell me a good packet/frame generator for linux? thanks manoj - 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 re

Re: Packet/frame generator

2001-03-30 Thread Manoj Sontakke
On Fri, 30 Mar 2001, Mircea Ciocan wrote: Here is a nice packet building library: www.packetfactory.net/Projects/Libnet/ its broken. Can anyone tell me a good packet/frame generator for linux? thanks manoj - To unsubscribe from this list: send the line "unsubs

Re: IP layer bug?

2001-03-25 Thread Manoj Sontakke
Hi, On Mon, 26 Mar 2001, Oleg Drokin wrote: > Hello! > > On Mon, Mar 26, 2001 at 04:06:19PM +0530, Manoj Sontakke wrote: > > >2.4.x kernel. have not tried 2.2 > > >I just found somethig, I believe is kernel bug. > > >I am working with usbne

Re: IP layer bug?

2001-03-25 Thread Manoj Sontakke
to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > -- Regards, Manoj Sontakke - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message t

Re: IP layer bug?

2001-03-25 Thread Manoj Sontakke
lease read the FAQ at http://www.tux.org/lkml/ -- Regards, Manoj Sontakke - 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

Re: IP layer bug?

2001-03-25 Thread Manoj Sontakke
Hi, On Mon, 26 Mar 2001, Oleg Drokin wrote: Hello! On Mon, Mar 26, 2001 at 04:06:19PM +0530, Manoj Sontakke wrote: 2.4.x kernel. have not tried 2.2 I just found somethig, I believe is kernel bug. I am working with usbnet.c driver, which stores some of its internal

Fib entries

2001-03-22 Thread Manoj Sontakke
the entries for delivery for all the 3 cases or only for the third case Thanks in advance for all the help Manoj - 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

Fib entries

2001-03-22 Thread Manoj Sontakke
the entries for delivery for all the 3 cases or only for the third case Thanks in advance for all the help Manoj - 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

Re: initialisation code

2001-03-21 Thread Manoj Sontakke
Hi Thanks for all the help. On Wed, 21 Mar 2001, Keith Owens wrote: > On Wed, 21 Mar 2001 22:00:51 +0530 (IST), > Manoj Sontakke <[EMAIL PROTECTED]> wrote: > > I have a initlisation function (just like pktsched_init in > >TC). Can anyone tell me, where in

initialisation code

2001-03-21 Thread Manoj Sontakke
have a initlisation function (just like pktsched_init in TC). Can anyone tell me, where in the kernel boot sequence should I make a call to my initialisation function. Thanks in advance for all the help. Manoj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" i

initialisation code

2001-03-21 Thread Manoj Sontakke
have a initlisation function (just like pktsched_init in TC). Can anyone tell me, where in the kernel boot sequence should I make a call to my initialisation function. Thanks in advance for all the help. Manoj - To unsubscribe from this list: send the line "unsubscribe linux-kernel" i

Re: initialisation code

2001-03-21 Thread Manoj Sontakke
Hi Thanks for all the help. On Wed, 21 Mar 2001, Keith Owens wrote: On Wed, 21 Mar 2001 22:00:51 +0530 (IST), Manoj Sontakke [EMAIL PROTECTED] wrote: I have a initlisation function (just like pktsched_init in TC). Can anyone tell me, where in the kernel boot sequence should I

quicksort for linked list

2001-03-08 Thread Manoj Sontakke
Hi Sorry, these questions do not belog here but i could not find any better place. 1. Is quicksort on doubly linked list is implemented anywhere? I need it for sk_buff queues. 2. Is Weighted Round Robin implemented in linux anyehere? thanks in advence. Manoj - To unsubscribe from

quicksort for linked list

2001-03-08 Thread Manoj Sontakke
Hi Sorry, these questions do not belog here but i could not find any better place. 1. Is quicksort on doubly linked list is implemented anywhere? I need it for sk_buff queues. 2. Is Weighted Round Robin implemented in linux anyehere? thanks in advence. Manoj - To unsubscribe from

Re: spinlock help

2001-03-07 Thread Manoj Sontakke
that possible that a 'spin_unlock_irqrestore(c,d)' would also restore > what should have been restored only with a 'spin_unlock_irqrestore(a,b)' ? > > Thanks in advance, > Shmulik Hen > Software Engineer > Linux Advanced Networking Services >

Re: spinlock help

2001-03-07 Thread Manoj Sontakke
Linux Advanced Networking Services Intel Network Communications Group Jerusalem, Israel. -Original Message- From: Nigel Gamble [mailto:[EMAIL PROTECTED]] Sent: Wednesday, March 07, 2001 1:54 AM To: Manoj Sontakke Cc: [EMAIL PROTECTED] Subject: Re: spinlock help On

spinlock help

2001-03-06 Thread Manoj Sontakke
Hi Thankx in idvance for the help. 1. when spin_lock_irqsave() function is called the subsequent code is executed untill spin_unloc_irqrestore()is called. is this right? 2. is this sequence valid? spin_lock_irqsave(a,b); spin_lock_irqsave(c,d); Manoj - To unsubscribe from

spinlock help

2001-03-06 Thread Manoj Sontakke
Hi Thankx in idvance for the help. 1. when spin_lock_irqsave() function is called the subsequent code is executed untill spin_unloc_irqrestore()is called. is this right? 2. is this sequence valid? spin_lock_irqsave(a,b); spin_lock_irqsave(c,d); Manoj - To unsubscribe from

<    1   2