2850 replies to this topic

[PaulOBrien]

The very eagerly awaited Advent Vega kernel source is now available!

I'm pleased to say that i've been working with DSG to help release the source ready for developers to work with straight away and with that in mind, the kernel source is available to download now from my GitHub.

You'll find two versions available - the standard one (which I have successfully compiled on Linux and deployed to my Vega) and a version for compilation on OSX (also successfully compiled and deployed). I've built my boot images using the mkbootimg arguments '--base 0x10000000 --pagesize 2048'. The Vega boot image ramdisk is also on my GitHub.

Let the fun begin!

P

[Buzing Bee]

Nice

Now working on it ..... shame it had to come out they day i go away

[martinbrook]

Hi Paul,

Nice one.

thanks

Paul, on Jan 28 2011, 16:07, said:

The very eagerly awaited Advent Vega kernel source is now available!

I'm pleased to say that i've been working with DSG to help release the source ready for developers to work with straight away and with that in mind, the kernel source is available to download now from my GitHub.

You'll find two versions available - the standard one (which I have successfully compiled on Linux and deployed to my Vega) and a version for compilation on OSX (also successfully compiled and deployed). I've built my boot images using the mkbootimg arguments '--base 0x10000000 --pagesize 2048'. The Vega boot image ramdisk is also on my GitHub.

Let the fun begin!

P

[harmohn]

Great news, nice work Paul!

[Pully]

Nice work, thanks for your continued efforts for the better of all users.

A nice little comment on their site too:

"This links to the Kernel source for Advent Vega - Kindly hosted by Paul over at MoDaCo.com - The premier enthusiast site for Android and Windows Mobile devices"

Amen to that

[ptbw]

harmohn, on Jan 28 2011, 15:39, said:

Great news, nice work Paul!

+1 to that.

Bit of a coup!

[rferrett]

Right, apologies if being a little dim here. What will the practical upshot of this bbe? Custom roms with gingerbread. And honeycomb components?

[gingercat]

rferrett, on Jan 28 2011, 16:07, said:

Right, apologies if being a little dim here. What will the practical upshot of this bbe? Custom roms with gingerbread. And honeycomb components?

A few posts down in the forum reveals info here

Edited by gingercat, 28 January 2011 - 04:10 PM.

[rvdgeer]

rferrett, on Jan 28 2011, 17:07, said:

Right, apologies if being a little dim here. What will the practical upshot of this bbe? Custom roms with gingerbread. And honeycomb components?

There is an entire topic on this exact question...
Maybe there's an answer in there too...

[martinbrook]

Hi Paul,

Will this git repo be used by the OEM for any updates?

vgrade

Paul, on Jan 28 2011, 16:07, said:

The very eagerly awaited Advent Vega kernel source is now available!

I'm pleased to say that i've been working with DSG to help release the source ready for developers to work with straight away and with that in mind, the kernel source is available to download now from my GitHub.

You'll find two versions available - the standard one (which I have successfully compiled on Linux and deployed to my Vega) and a version for compilation on OSX (also successfully compiled and deployed). I've built my boot images using the mkbootimg arguments '--base 0x10000000 --pagesize 2048'. The Vega boot image ramdisk is also on my GitHub.

Let the fun begin!

P

[SilentMobius]

Thanks for all your hard work Paul.

Do we know which touch screen driver is being used yet? I can see:

CONFIG_TOUCHSCREEN_EGALAX=y
CONFIG_TOUCHSCREEN_IT7260=y
CONFIG_TOUCHSCREEN_USB_COMPOSITE=y
CONFIG_TOUCHSCREEN_USB_EGALAX=y
CONFIG_TOUCHSCREEN_USB_PANJIT=y
CONFIG_TOUCHSCREEN_USB_JASTEC=y
CONFIG_TOUCHSCREEN_USB_E2I=y

Configured in the kernel but I don't have lsusb or lspci to check what's available on the vega. I'm hoping something can be done to prevent "sticky" touch points, but the first think I'd like to do is start logging something (well I'd like to compile my own kernel first, after that I'll make changes )

I only see EGALAX code in the source and I see a .old in there as well maybe that's it.

Edited by SilentMobius, 28 January 2011 - 04:55 PM.

[HunteronX]

Nice one - thanks Paul!  

[azareus22]

Hello

I need clean kernel source code, not modified source from git...

If the kernel source is GPL, I do not understand why is hosted on a external git from Advent, which has been modified.

Thanks

Paul, on Jan 28 2011, 16:07, said:

The very eagerly awaited Advent Vega kernel source is now available!

I'm pleased to say that i've been working with DSG to help release the source ready for developers to work with straight away and with that in mind, the kernel source is available to download now from my GitHub.

You'll find two versions available - the standard one (which I have successfully compiled on Linux and deployed to my Vega) and a version for compilation on OSX (also successfully compiled and deployed). I've built my boot images using the mkbootimg arguments '--base 0x10000000 --pagesize 2048'. The Vega boot image ramdisk is also on my GitHub.

Let the fun begin!

P

[OwenRW]

azareus22, on Jan 28 2011, 23:30, said:

Hello

I need clean kernel source code, not modified source from git...

If the kernel source is GPL, I do not understand why is hosted on a external git from Advent, which has been modified.

Thanks

If you can't undo the change listed in the "USB connectivity / suspend fix (patch_for_DIX)" commit yourself, then I don't think the kernel source is going to be much use to you...

[martinbrook]

Hi Guys,

Has anyone got a .config file from the Mobii which has USB host enabled? OK sorted now.

vgrade

OwenRW, on Jan 29 2011, 01:13, said:

If you can't undo the change listed in the "USB connectivity / suspend fix (patch_for_DIX)" commit yourself, then I don't think the kernel source is going to be much use to you...

Edited by martinbrook, 29 January 2011 - 02:11 PM.

[azareus22]

OwenRW, on Jan 29 2011, 01:13, said:

If you can't undo the change listed in the "USB connectivity / suspend fix (patch_for_DIX)" commit yourself, then I don't think the kernel source is going to be much use to you...

I work with svn and git and I know how to do reverts, but it is not normal to have to reverse the changes to have the original source code, this has a name... fork .

martinbrook, on Jan 29 2011, 14:37, said:

Hi Guys,

Has anyone got a .config file from the Mobii which has USB host enabled? OK sorted now.

vgrade

In https://github.com/p...dm_query.c#L718 Usb2Property is asigned with NvOdmUsbModeType_Host.

In https://github.com/p...dm_query.h#L967 it defines NvOdmUsbModeType_Host and NvOdmUsbModeType_Device

Changing Usb2Property or Usb3Property is probable that we can change host to slave. I think that Usb2Property is the USB controller for touchscreen eGalax and camera.

Edited by azareus22, 29 January 2011 - 02:34 PM.

[PaulOBrien]

azareus22, on Jan 28 2011, 23:30, said:

Hello

I need clean kernel source code, not modified source from git...

If the kernel source is GPL, I do not understand why is hosted on a external git from Advent, which has been modified.

Thanks

I'm kinda confused.

Download the initial commit and that's what I guess you are calling 'clean source'. As an expert on GIT / SVN you are well aware that uploading the source doesn't change it. That's what was supplied originally from the manufacturers.

However, what was originally supplied from the manufacturers didn't work properly on the Vega, hence the patches, which are clearly labelled additional commits.

The reason i'm confused is that doing things this way you have all the benefits of the normal '.tar.gz' distribution (it's clean and unmodified), but with the added benefit of having fixes to make the thing actually work on our devices.

If you want me to supply you the original tar.gz I can do that (in fact, you can get the initial commit directly from github in tar.gz format here), but it's IDENTICAL to the initial commit (as I said) for obvious reasons.

Care to explain a bit more clearly what you want exactly?

Cheers!

P

[azareus22]

Paul, on Jan 29 2011, 17:40, said:

I'm kinda confused.

Download the initial commit and that's what I guess you are calling 'clean source'. As an expert on GIT / SVN you are well aware that uploading the source doesn't change it. That's what was supplied originally from the manufacturers.

However, what was originally supplied from the manufacturers didn't work properly on the Vega, hence the patches, which are clearly labelled additional commits.

The reason i'm confused is that doing things this way you have all the benefits of the normal '.tar.gz' distribution (it's clean and unmodified), but with the added benefit of having fixes to make the thing actually work on our devices.

If you want me to supply you the original tar.gz I can do that (in fact, you can get the initial commit directly from github in tar.gz format here), but it's IDENTICAL to the initial commit (as I said) for obvious reasons.

Care to explain a bit more clearly what you want exactly?

Cheers!

P

Hello Paul

My question was basically, if you apply patches to your advent git, Do these patches will be yours or only the Advent has given you? How do we differentiate? this is what confuses me.

On the other hand, if Advent can to place directly the code in their website, I guess if you and Advent have reached any agreement about source code?.

Thanks

[SilentMobius]

azareus22, on Jan 29 2011, 19:59, said:

Hello Paul

My question was basically, if you apply patches to your advent git, Do these patches will be yours or only the Advent has given you? How do we differentiate? this is what confuses me.

On the other hand, if Advent can to place directly the code in their website, I guess if you and Advent have reached any agreement about source code?.

Thanks

Just so you know, your English is terrible and thus what you're asking is _still_ not clear.

Advent gave Paul a tar.gz of the kernel source.
Paul created a git repo for us to use (thanks Paul)
Paul has continued to work on _his_ repo adding some fixes and other useful stuff.

Advent are unlikely to give us _anything_ else at this stage (They are an OEM, and most likely do none of the development work)

[PaulOBrien]

azareus22, on Jan 29 2011, 19:59, said:

Hello Paul

My question was basically, if you apply patches to your advent git, Do these patches will be yours or only the Advent has given you? How do we differentiate? this is what confuses me.

On the other hand, if Advent can to place directly the code in their website, I guess if you and Advent have reached any agreement about source code?.

Thanks

I'll fork it (well, probably create a new branch) for my own changes. Simples. What you see on master is the Advent release. What you see on the OSX branch is the Advent release modified to compile on OSX. There'll be a MCK branch in due course.

P