Skip to contentSkip to conversation

How to compile kernel for Geode GX1

DISCUSSION Jocelyn Mayer 3 participants 3 messages May 9, 2001 Kbuild

lore
Share & tools
lore
#0 lore raw
Quoted 8 lines

Hi,

How can I compile a kernel that would be running on a National Semiconductor Geode GX1 processor?

I wish to be personally CC'ed the answers/comments posted to the list in response to my posting. Thank you.

Best Regards,
Anton

Well, you can select '(586/K5/5x86/6x86/6x86MX) Processor family ' in the 'Processor type and features ' menu of menuconfig.

That's what I do for a Geode GXLv,
and it works with 2.2 and 2.4 kernels.
There is one version (maybe more ?),
I think 2.4.1, which cannot boot on Cyrix,
but others works well...

Regards.

#1 lore raw

If you are using the vesa framebuffer on the Geode, you will also want to make a minor change to vesafb.c. Because the framebuffer is located within the processor itself, requesting the memory region always caused my Geode boxes to freeze. I think that we can safely eliminate this call, since we know the memory is always available:

vesafb.c renamed from usr/src/linux/drivers/video/vesafb.c +2 -0
@@ -519,12 +519,14 @@
 	video_visual = (video_bpp == 8) ?
 		FB_VISUAL_PSEUDOCOLOR : FB_VISUAL_TRUECOLOR;
 
+#ifdef NOTUSED
 	if (!request_mem_region(video_base, video_size, "vesafb")) {
 		printk(KERN_ERR
 		       "vesafb: abort, cannot reserve video memory at 0x%lx\n",
 			video_base);
 		return -EBUSY;
 	}
+#endif
 
         video_vbase = ioremap(video_base, video_size);
 	if (!video_vbase) {

Jordan

Signature · 1 line
-- embed this!  http://www.microwindows.org --
#2 lore raw
Quoted 5 lines

If you are using the vesa framebuffer on the Geode, you will also want to make a minor change to vesafb.c. Because the framebuffer is located within the processor itself, requesting the memory region always caused my Geode boxes to freeze. I think that we can safely eliminate this call, since we know the memory is always available:

That actually looks like a correct change. The Geode and one or two other devices use memory that may well not be visible in the system map. Being unable to map the memory in the vesafb case is worth a warning but not fatal