Dear All,
I have a simple problem in doing modprobe of ndiswrapper in case of driver
of Intel Corporation PRO/Wireless 3945ABG Network Connection [8086:4222]
card. The steps which I mentioned is as follows. Please help me if I am
missing something. Sorry, this is specific about ndiswrapper, but
Dear All,
In a NUMA enabled system, can we use taskset to bind process/thread
to specific processor.
According to following documentation, taskset does not work with NUMA system.
Hi
Thanks for your reply
On Tue, Aug 11, 2009 at 10:38 AM, Mulyadi Santosa mulyadi.sant...@gmail.com
wrote:
Hello
On Mon, Aug 10, 2009 at 11:07 PM, Basavaraj
Dengibasavarajde...@gmail.com wrote:
I am porting 'kdb' to omap3430 platform.
for command 'mdp arg' [mdp is memory dump physical
On Tue, 11 Aug 2009 11:37:03 +0530
er krishna erkris...@gmail.com wrote:
I have a simple problem in doing modprobe of ndiswrapper in case of
driver of Intel Corporation PRO/Wireless 3945ABG Network Connection
[8086:4222] card. The steps which I mentioned is as follows. Please
help me if I am
On Tue, Aug 11, 2009 at 3:17 PM, Erik Mouw m...@nl.linux.org wrote:
On Tue, 11 Aug 2009 11:37:03 +0530
er krishna erkris...@gmail.com wrote:
I have a simple problem in doing modprobe of ndiswrapper in case of
driver of Intel Corporation PRO/Wireless 3945ABG Network Connection
[8086:4222]
Hi All,
I am working on Porting of a windows device driver to Linux. Windows has a
notion of Queued Spinlock. I could not understand how it is different than
normal spinlock, the document says it is faster than a normal spinlock.
If any one is having more information on Queued Spinlock, please
On Tue, Aug 11, 2009 at 4:12 PM, Prasad Joshiprasadjoshi...@gmail.com wrote:
Hi All,
I am working on Porting of a windows device driver to Linux. Windows has a
notion of Queued Spinlock. I could not understand how it is different than
normal spinlock, the document says it is faster than a
Kernel and module debugging with gdb: http://cli.gs/LHaA4a.
Enjoy.
rday
--
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web
On Tue, 2009-08-11 at 13:03 -0400, Robert P. J. Day wrote:
Kernel and module debugging with gdb: http://cli.gs/LHaA4a.
Enjoy.
rday
--
Robert P. J. Day Waterloo, Ontario, CANADA
On Wed, 12 Aug 2009, Microbit_Ubuntu wrote:
Hi Robert and all,
The article is quite interesting, however it seems hard to scratch
together relevant (should read : not outdated thus wrong) on
debugging kernel modules on a *remote* target...
the plan is for that to be a column down the
On Tue, 2009-08-11 at 14:41 -0400, Robert P. J. Day wrote:
On Wed, 12 Aug 2009, Microbit_Ubuntu wrote:
Hi Robert and all,
The article is quite interesting, however it seems hard to scratch
together relevant (should read : not outdated thus wrong) on
debugging kernel modules on a
I've been trying to create a system with a read-only rootfs using initramfs,
but I'm not having any luck. I've included ro on my command line and when
I cat /proc/cmdline it reports ro like I expect. But when I type mount,
I see this:
rootfs on / type rootfs (rw)
And I can create new files
Hi,
I was going through this code below and was confused why do we need
lock ordering here. What is the problem that it is trying to prevent
given that the corresponding unlocking doesn't care for the order. I
assume lock orders are primarily needed to avoid deadlocks, and if
they are then they
I haven't looked the code but ...
You can unlock in any order, right ? because whatever happens you will
always be able to unlock and it the locks are acquired in the same order
throughout the system, then your system is guaranteed to make forward
progress.
As an exercise try coming up with
14 matches
Mail list logo
