> Well, I applied the patch (in 2.6.23 it's
> arch/i386/boot/pmjump.S,
> not
> arch/x86/boot/pmjump.S,
> but that's minor) - still the same behavior, it still reboots
> instantly right when bootloader gave control to the kernel.
> So it must be something else.. ;)
It should be x86, they merged
Well, I applied the patch (in 2.6.23 it's
arch/i386/boot/pmjump.S,
not
arch/x86/boot/pmjump.S,
but that's minor) - still the same behavior, it still reboots
instantly right when bootloader gave control to the kernel.
So it must be something else.. ;)
It should be x86, they merged the
>
> On 7/11/07, Gerb Stralko <[EMAIL PROTECTED]> wrote:
> [...]
> > This link will help:
> > http://www.ii.com/internet/messaging/pine/pc/#gmail
> >
> > Scroll down untill you see a yellow box section that say:
> > Gmail Tips
> > * If you w
2) If you have a box available at home (or elsewhere), use that to
relay mail through.
read linux mail from you gmail account. When you need to send a patch,
send it from a linux box using pine, but change the From to your gmail
account. Like Jesper suggested works great! Best of both
2) If you have a box available at home (or elsewhere), use that to
relay mail through.
read linux mail from you gmail account. When you need to send a patch,
send it from a linux box using pine, but change the From to your gmail
account. Like Jesper suggested works great! Best of both
do you have ssh access? if so, setup a linux machine outside of this
evil network and ssh into it. ssh is pretty configurable to get
around firewalls/nats.
enjoy
On 7/11/07, Satyam Sharma [EMAIL PROTECTED] wrote:
On 7/11/07, Satyam Sharma [EMAIL PROTECTED] wrote:
Hi,
On 7/11/07, Gerb
On 5/23/07, Russell King <[EMAIL PROTECTED]> wrote:
On Wed, May 23, 2007 at 01:27:11PM -0400, Gerb Stralko wrote:
> Use the kernel wide ARRAY_SIZE when determining the array size of a struct.
>
> Signed-off-by: Jerry Stralko <[EMAIL PROTECTED]>
Whitespace damanged patch,
Use the kernel wide ARRAY_SIZE when determining the array size of a struct.
Signed-off-by: Jerry Stralko <[EMAIL PROTECTED]>
---
diff --git a/arch/arm/kernel/dma-isa.c b/arch/arm/kernel/dma-isa.c
index 0a3e9ad..c94ad71 100644
--- a/arch/arm/kernel/dma-isa.c
+++ b/arch/arm/kernel/dma-isa.c
@@
Use the kernel wide ARRAY_SIZE when determining the array size of a struct.
Signed-off-by: Jerry Stralko [EMAIL PROTECTED]
---
diff --git a/arch/arm/kernel/dma-isa.c b/arch/arm/kernel/dma-isa.c
index 0a3e9ad..c94ad71 100644
--- a/arch/arm/kernel/dma-isa.c
+++ b/arch/arm/kernel/dma-isa.c
@@
On 5/23/07, Russell King [EMAIL PROTECTED] wrote:
On Wed, May 23, 2007 at 01:27:11PM -0400, Gerb Stralko wrote:
Use the kernel wide ARRAY_SIZE when determining the array size of a struct.
Signed-off-by: Jerry Stralko [EMAIL PROTECTED]
Whitespace damanged patch, probably due to using format
Please don't do this. Using the same name for a branch as for a tag is
madness. Call it "v2.6.20-stable" or anything else, but don't re-use the
same naming as for tags.
Yes I have done this before, and it took me awhile to realize what was
going on. It caused me some grief, and a few hours of
Please don't do this. Using the same name for a branch as for a tag is
madness. Call it v2.6.20-stable or anything else, but don't re-use the
same naming as for tags.
Yes I have done this before, and it took me awhile to realize what was
going on. It caused me some grief, and a few hours of
http://www.netnice.org/
it does exactly that...this project started at my college, and we've
done some cool research with this little project. Take a look, alot of
research papers too...
On 3/30/07, Pavel Machek <[EMAIL PROTECTED]> wrote:
Hi!
> I've been hacking on the Linux kernel all
http://www.netnice.org/
it does exactly that...this project started at my college, and we've
done some cool research with this little project. Take a look, alot of
research papers too...
On 3/30/07, Pavel Machek [EMAIL PROTECTED] wrote:
Hi!
I've been hacking on the Linux kernel all semester
+/* data port used by apple SMC */
+#define APPLESMC_DATA_PORT 0x300
+/* command/status port used by apple SMC */
+#define APPLESMC_CMD_PORT 0x304
+
+#define APPLESMC_NR_PORTS 5 /* 0x300-0x304 */
+
+#define APPLESMC_STATUS_MASK 0x0f
+#define APPLESMC_READ_CMD 0x10
+#define
+/* data port used by apple SMC */
+#define APPLESMC_DATA_PORT 0x300
+/* command/status port used by apple SMC */
+#define APPLESMC_CMD_PORT 0x304
+
+#define APPLESMC_NR_PORTS 5 /* 0x300-0x304 */
+
+#define APPLESMC_STATUS_MASK 0x0f
+#define APPLESMC_READ_CMD 0x10
+#define
I am writing a kernel module that creates a kernel thread on a SMP
platform.
How to get the ID of the processor the kernel thread run on? Have any
kernel API? THX
Raymond
try smp_processor_id() it returns an unsigned int.
Thanks,
jerry
-
To unsubscribe from this list: send the line
I am writing a kernel module that creates a kernel thread on a SMP
platform.
How to get the ID of the processor the kernel thread run on? Have any
kernel API? THX
Raymond
try smp_processor_id() it returns an unsigned int.
Thanks,
jerry
-
To unsubscribe from this list: send the line
18 matches
Mail list logo
