Jump to content


Photo

Kernel 2.6.36 build for Vega


  • Please log in to reply
10 replies to this topic

#1
dconde

dconde

    Newbie

  • Members
  • Pip
  • 11 posts
I've been trying to build the correct kernel version for honeycomb from the android AOSP repository. I took the config from the Vega kernel that Paul released but I'm failing to build the Ventana parts. I see these are enabled in the config for the Vega. Does anyone know if these are actually needed and if so why if the Vega is based off of Harmony?

Edited by dconde, 01 March 2011 - 11:31 AM.

  • 0

#2
the_corvus

the_corvus

    Enthusiast

  • Members
  • PipPipPip
  • 200 posts

I've been trying to build the correct kernel version for honeycomb from the android AOSP repository. I took the config from the Vega kernel that Paul released but I'm failing to build the Ventana parts. I see these are enabled in the config for the Vega. Does anyone know if these are actually needed and if so why if the Vega is based off of Harmony?


When i try to compile this is what i get:

CC fs/yaffs2/yaffs_fs.o
fs/yaffs2/yaffs_fs.c:400: error: unknown field 'delete_inode' specified in initializer
fs/yaffs2/yaffs_fs.c:400: warning: initialization from incompatible pointer type
fs/yaffs2/yaffs_fs.c:401: error: unknown field 'clear_inode' specified in initializer
fs/yaffs2/yaffs_fs.c:401: warning: initialization from incompatible pointer type
fs/yaffs2/yaffs_fs.c: In function 'yaffs_delete_inode':
fs/yaffs2/yaffs_fs.c:799: error: implicit declaration of function 'clear_inode'
fs/yaffs2/yaffs_fs.c: In function 'yaffs_setattr':
fs/yaffs2/yaffs_fs.c:1823: error: implicit declaration of function 'inode_setattr'
make[2]: *** [fs/yaffs2/yaffs_fs.o] Error 1
make[1]: *** [fs/yaffs2] Error 2
make: *** [fs] Error 2

Did you get this fixed?

I'm trying to not compile the unnecesary modules, like cifs and so on, but yaffs is realy needed.

Corvus

  • 0
If you like my work, you can buy me some beer... Press here.

If you have a problem, i will spend the same time helping you than you've spent for asking for help, so write a detailed description of your problem.

#3
dconde

dconde

    Newbie

  • Members
  • Pip
  • 11 posts

When i try to compile this is what i get:

CC fs/yaffs2/yaffs_fs.o
fs/yaffs2/yaffs_fs.c:400: error: unknown field 'delete_inode' specified in initializer
fs/yaffs2/yaffs_fs.c:400: warning: initialization from incompatible pointer type
fs/yaffs2/yaffs_fs.c:401: error: unknown field 'clear_inode' specified in initializer
fs/yaffs2/yaffs_fs.c:401: warning: initialization from incompatible pointer type
fs/yaffs2/yaffs_fs.c: In function 'yaffs_delete_inode':
fs/yaffs2/yaffs_fs.c:799: error: implicit declaration of function 'clear_inode'
fs/yaffs2/yaffs_fs.c: In function 'yaffs_setattr':
fs/yaffs2/yaffs_fs.c:1823: error: implicit declaration of function 'inode_setattr'
make[2]: *** [fs/yaffs2/yaffs_fs.o] Error 1
make[1]: *** [fs/yaffs2] Error 2
make: *** [fs] Error 2

Did you get this fixed?

I'm trying to not compile the unnecesary modules, like cifs and so on, but yaffs is realy needed.

Corvus



Yep,

Pull in the latest yaffs2 from 'git clone git://www.aleph1.co.uk/yaffs2' and copy it into fs/yaffs2/.

  • 0

#4
simonta

simonta

    Hardcore

  • Members
  • PipPipPipPipPipPip
  • 1,298 posts
  • Gender:Male
  • Location:Southampton
  • Devices:Vega. HTC Desire
Honest answer is that I have no idea, but as the Ventana chipset has only just shipped (if indeed it has, I think it was due end Feb), I'd be reasonably confident that they're linked but not used..one sure way to find out :huh:

  • 0
If I've helped you, you want to say "thanks" and you do not use Dropbox (it's enormously useful, especially with mobile devices), please consider signing up for it using my reference. You'll get 2GB of disk space for files available anywhere, any time on any device. They give us both an extra 250MB if you do sign up!

Sign up for Dropbox

Apple? I'd rather eat my own kidneys!

#5
dconde

dconde

    Newbie

  • Members
  • Pip
  • 11 posts

Honest answer is that I have no idea, but as the Ventana chipset has only just shipped (if indeed it has, I think it was due end Feb), I'd be reasonably confident that they're linked but not used..one sure way to find out :)


Aye, I tried booting the Vega from the kernel built without it yesterday evening but just got a blank screen. It might have been something else that was missing though as it was late when I was trying it.

I did manage to get to an adb shell with the Xoom system image, Xoom ramdisk and the original Vega kernel a few days ago but some services wouldn't start, hence the trying to build the new kernel :huh:

Edited by dconde, 01 March 2011 - 12:42 PM.

  • 0

#6
the_corvus

the_corvus

    Enthusiast

  • Members
  • PipPipPip
  • 200 posts

Aye, I tried booting the Vega from the kernel built without it yesterday evening but just got a blank screen. It might have been something else that was missing though as it was late when I was trying it.

I did manage to get to an adb shell with the Xoom system image, Xoom ramdisk and the original Vega kernel a few days ago but some services wouldn't start, hence the trying to build the new kernel :huh:


I try this too but the xoom system img is more than 180Mb and system partition in my advent is less that 135Mb. I try to delete many things and at least i get a 120Mb system, but i forgot to use the xoom ramdisk :S, so i get a rebooting loop.

All the odex files cant be deleted???

I'm just recloning tegra git, because some strange things are happening... so better start again.

Corvus.

  • 0
If you like my work, you can buy me some beer... Press here.

If you have a problem, i will spend the same time helping you than you've spent for asking for help, so write a detailed description of your problem.

#7
dconde

dconde

    Newbie

  • Members
  • Pip
  • 11 posts

I try this too but the xoom system img is more than 180Mb and system partition in my advent is less that 135Mb. I try to delete many things and at least i get a 120Mb system, but i forgot to use the xoom ramdisk :S, so i get a rebooting loop.

All the odex files cant be deleted???

I'm just recloning tegra git, because some strange things are happening... so better start again.

Corvus.


I've been using fastboot for flashing images etc

  • 0

#8
the_corvus

the_corvus

    Enthusiast

  • Members
  • PipPipPip
  • 200 posts

I've been using fastboot for flashing images etc



Sorry by my noob questions... but now i get this errors:

fs/yaffs2/yaffs_mtdif2_multi.c: In function 'nandmtd2_write_chunk_tags':
fs/yaffs2/yaffs_mtdif2_multi.c:54: error: implicit declaration of function 'yaffs_trace'
make[2]: *** [fs/yaffs2/yaffs_mtdif2_multi.o] Error 1
make[1]: *** [fs/yaffs2] Error 2
make: *** [fs] Error 2


I have copied the yaffs2 files from the git to fs/yaffs2.

I try to compare the original files with git ones but i dont find any clue to solve this.

Corvus.

PD: I promise be more valuable once we get kernel working :huh:

  • 0
If you like my work, you can buy me some beer... Press here.

If you have a problem, i will spend the same time helping you than you've spent for asking for help, so write a detailed description of your problem.

#9
Kentaree

Kentaree

    Newbie

  • Members
  • Pip
  • 2 posts

Sorry by my noob questions... but now i get this errors:

fs/yaffs2/yaffs_mtdif2_multi.c: In function 'nandmtd2_write_chunk_tags':
fs/yaffs2/yaffs_mtdif2_multi.c:54: error: implicit declaration of function 'yaffs_trace'
make[2]: *** [fs/yaffs2/yaffs_mtdif2_multi.o] Error 1
make[1]: *** [fs/yaffs2] Error 2
make: *** [fs] Error 2
I have copied the yaffs2 files from the git to fs/yaffs2.

I try to compare the original files with git ones but i dont find any clue to solve this.

Corvus.

PD: I promise be more valuable once we get kernel working :huh:


In the yaffs2 dir that you got from git there should be a file called patch-ker.sh, which copies over the right files and makes sure Kconfig etc is updated. Remove the fs/yaffs2 folder in your kernel tree, then go to your yaff2 git working directory and run
./patch-ker.sh c m </path/to/kernel>
and it should copy and patch everything you need. When I run it it gives me an error saying it can't remove yaffs*.mod.c, but it doesn't seem to affect compilation as it gets past the yaffs building for me afterwards

  • 0

#10
the_corvus

the_corvus

    Enthusiast

  • Members
  • PipPipPip
  • 200 posts
Thank you very much...

With this i just get the same Ventana problem. But i try to bypass it changing nvhost_ by platform_ (this is used in all the others files). Then it will compile... but with the same result, black screen and no usb connection.

And i'm getting tired of reflash full rom and then modaco, so can someone explain me how to enter fastboot mode so i can test kernels without reflash?

Thanks.

Corvus.

Edited by the_corvus, 02 March 2011 - 11:39 AM.

  • 0
If you like my work, you can buy me some beer... Press here.

If you have a problem, i will spend the same time helping you than you've spent for asking for help, so write a detailed description of your problem.

#11
dconde

dconde

    Newbie

  • Members
  • Pip
  • 11 posts

Thank you very much...

With this i just get the same Ventana problem. But i try to bypass it changing nvhost_ by platform_ (this is used in all the others files). Then it will compile... but with the same result, black screen and no usb connection.

And i'm getting tired of reflash full rom and then modaco, so can someone explain me how to enter fastboot mode so i can test kernels without reflash?

Thanks.

Corvus.


To get into fastboot mode you need to remove your boot.img partition which makes the board go into fastboot mode on boot.

Put the device into apx mode using the button presses that you use before you flash the firmware.

Then using nvflash issue the following command 'nvflash --bl bootloader.bin --go -w'. The device will then wait for an instruction. Use 'nvflash --resume --format_partition 7' to remove the boot partition. Power up the device and you should see it waiting for a fastboot connection.

I couldn't get fastboot to connect to the device using windows 7 x64 but it connected fine using OSX or linux.

  • 0




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users