• Announcements

    • PaulOBrien

      Reminder - MoDaCo position on illegal content   07/30/15

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such software Nintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance) CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission) ROMs must give full credit to the original author ISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • PaulOBrien

      Reminder: Selling items on the forum directly is not allowed   07/30/15

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.
dconde

Kernel 2.6.36 build for Vega

11 posts in this topic

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
0

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites
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
0

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites

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
0

Share this post


Link to post
Share on other sites
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

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2016. MoDaCo uses IntelliTxt technology.