Major changes in froyo-x86 branch

[Chih-Wei Huang]

Hi developers,
There are some major changes in the froyo-x86 branch
recently that you should notice:

* The code base is updated to Android 2.2.2,
build id FRG83G.

* The kernel is switched to android-2.6.38,
with better drivers support. Especially,
I have merged the hid-multitouch driver
from Enac. It's aimed to replace other
multitouch drivers like hid-cando, hid-egalax,
hid-hanvon and hid-mozart (not yet).
If you're using these drivers, you need to
update your defconfig to use the new driver.
(see tegav2 as an example)

* To unify the place of common files, the
keymaps, firmware and app dirs are moved
from build to device/common, like
gingerbread-x86.

* Mesa & drm are updated to latest development branches.
Especially, mesa has large improvements:
- OpenGL ES 2 support
- dri driver auto-loaded mechanism. That means you can
define multiple dri driver in the same target
if you want to support all of them.
- experimentally support Radeon chipset. You have to
define BOARD_USES_R600G=true to enable it.
(see asus_laptop as an example)
A bonus: live wallpapers now work.

For targets maintainers, please update your
configs and test with the new code base.

I'm going to release Android-x86 2.2-r2
once several pending targets are published.

--
Chih-Wei
Android-x86 project
http://www.android-x86.org

[SriramR]

great - waiting for the new build..

(i have just joined this group..this project sounds very promising and
exciting !)

[Arobase40]

Sounds like mesa and drm are broken with FRG83G build ID ??? ^^

Unable to have a display whether with auto-detect or modprobe.
Just a black display with a blinking cursor !

I use the same defnition config files with the Acer 1825ptz.

EXTMOD="$EXTMOD acer-wmi"
UVESA_MODE=${UVESA_MODE:-1366x768}
FB0DEV=i965C

acer-wmi don't load any more and graphic display remains with i915
driver preventing from having i965C. :(

Anybody else encountered the same problems ?

[Chih-Wei Huang]

2011/4/12 Arobase40 <arob...@gmail.com>:

> Sounds like mesa and drm are broken with FRG83G build ID ??? ^^

No, it is not.

> Unable to have a display whether with auto-detect or modprobe.
> Just a black display with a blinking cursor !
>
> I use the same defnition config files with the Acer 1825ptz.
>
>                        EXTMOD="$EXTMOD acer-wmi"
>                        UVESA_MODE=${UVESA_MODE:-1366x768}
>                        FB0DEV=i965C
>
> acer-wmi don't load any more and graphic display remains with i915
> driver preventing from having i965C. :(

FB0DEV=i915

it's the kernel driver name. What you need is

BOARD_USES_I965C:=true

in your BoardConfig.mk.

I think I've explained i915, i915c, i965c clearly.
If you forgot, read the previous post again.

However, except EXTMOD, all others are unnecessary
and can be removed if you're using auto-detect.

[Arobase40]

I know all this Chih Wei,

As already explained, this is the same configuration files as with the
previous Build ID.

BOARD_USES_I965C:=true was already set in the BoardConfig.mk file.

EXTMOD="$EXTMOD acer-wmi" also worked with the previous build and
don't work anymore now ! :(


On 12 avr, 03:42, Chih-Wei Huang <cwhu...@android-x86.org> wrote:
> 2011/4/12 Arobase40 <arobas...@gmail.com>:

[Arobase40]

Hi Chih Wei,

I got exactly the same problem and issue with your stock asus_laptop
target.

[Chih-Wei Huang]

Then I don't know what your problem is.

All the targets I pushed have been tested fine.

Have you tried a clean build?

2011/4/12 Arobase40 <arob...@gmail.com>:

> Hi Chih Wei,
> I got exactly the same problem and issue with your stock asus_laptop
> target.

--

[Arobase40]

Yes I did a clean build both with my own target and the asus_laptop
target.

The first time I got this issue was after I applied the mesa external
upgrade as mentioned in your previous post here :

http://groups.google.com/group/android-x86/browse_thread/thread/874c6ba62ce6b550/ac20534d5ddc048e

and then repo sync so I got this FRG83G build id.

I then deleted completely Android-x86 Froyo 2.2 version and restored a
clean Froyo-x86 2.1 version and repo sync again.

But the problem remains just the same. :(

What sounds strange is that the same iso files (Acer 1825ptz or
Asus_laptop) does work fine within VirtualBox, but does not with my
Acer 1825ptz hardware whatever res is chosen : MDPI, HDPI, Vesa or
Debug mode with nomodeset option !!! ^^

So I'll stay with Froyo-x86 2.1 for the moment, until an issue is
found out... :(

On 12 avr, 09:56, Chih-Wei Huang <cwhu...@android-x86.org> wrote:
> Then I don't know what your problem is.
>
> All the targets I pushed have been tested fine.
>
> Have you tried a clean build?
>

> 2011/4/12 Arobase40 <arobas...@gmail.com>:

[Chih-Wei Huang]

Oops! Did I mention any special action
to get mesa in THIS post?

Everything is now in our repository and
what you need to do is just repo sync.

The olv's mesa repository has entered
the next stage which aimed to honeycomb.

2011/4/12 Arobase40 <arob...@gmail.com>:

> Yes I did a clean build both with my own target and the asus_laptop
> target.
>
> The first time I got this issue was after I applied the mesa external
> upgrade as mentioned in your previous post here :
>
> http://groups.google.com/group/android-x86/browse_thread/thread/874c6ba62ce6b550/ac20534d5ddc048e
>
> and then repo sync so I got this FRG83G build id.
>
> I then deleted completely Android-x86 Froyo 2.2 version and restored a
> clean Froyo-x86 2.1 version and repo sync again.
>
> But the problem remains just the same. :(
>
> What sounds strange is that the same iso files (Acer 1825ptz or
> Asus_laptop) does work fine within VirtualBox, but does not with my
> Acer 1825ptz hardware whatever res is chosen : MDPI, HDPI, Vesa or
> Debug mode with nomodeset option !!! ^^

That's because on a vm the hw acceleration is disabled.
(Technically speaking, the bootstrap script will
detect if a dri device is available. If not,
set HWACCEL=0)

> So I'll stay with Froyo-x86 2.1 for the moment, until an issue is
> found out... :(

--

[Arobase40]

Oops ! Didn't I say I made the mesa upgrade BEFORE you posted this
message, and then DOWNGRADED with a previous backup to then apply a
repo sync on an "old" MASTER build ID 2.2.1 (Ok, I made a typo when I
called it 2.1) ??? ;-)

Anyway, I'll download again a fresh copy of Froyo FRG83G build id when
I get spare time, just to be sure. I'll waste some six hours or more,
depending on my internet connexion. But at least, I'll know if that
comes from my actual backup or from the git server... ^^ :-/

On 13 avr, 03:23, Chih-Wei Huang <cwhu...@android-x86.org> wrote:
> Oops! Did I mention any special action
> to get mesa in THIS post?
>
> Everything is now in our repository and
> what you need to do is just repo sync.
>
> The olv's mesa repository has entered
> the next stage which aimed to honeycomb.
>

> 2011/4/12 Arobase40 <arobas...@gmail.com>:

>
>
>
>
>
>
>
>
>
> > Yes I did a clean build both with my own target and the asus_laptop
> > target.
>
> > The first time I got this issue was after I applied the mesa external
> > upgrade as mentioned in your previous post here :
>

> >http://groups.google.com/group/android-x86/browse_thread/thread/874c6...

[Chih-Wei Huang]

2011/4/13 Arobase40 <arob...@gmail.com>:

> Oops ! Didn't I say I made the mesa upgrade BEFORE you posted this
> message, and then DOWNGRADED with a previous backup to then apply a
> repo sync on an "old" MASTER build ID 2.2.1 (Ok, I made a typo when I
> called it 2.1) ??? ;-)

I don't really understand what you did or
whether if it's correct.

Let me emphasis again.
What you have to do is just
'repo sync'.
It ensures your codebase will
sync with the latest froyo-x86 tree.

> Anyway, I'll download again a fresh copy of Froyo FRG83G build id when
> I get spare time, just to be sure. I'll waste some six hours or more,
> depending on my internet connexion. But at least, I'll know if that
> comes from my actual backup or from the git server... ^^ :-/

No need to do a fresh copy. Just 'repo sync' again.

If doubt, enter any project (e.g., external/mesa) and issue
git branch --vva, check if your HEAD commit id is the same
as commit id of x86/froyo-x86.
(the HEAD of external/mesa should be 559a79f)

[StefanS]

Hi Chih-Wei,

I have now tested the latest branch, and everything works fine (e.g. wacom-input, thanks), BUT my I915C is very "slow". This means, it looks a bit like the fps (frames per second) are capped. I have a i915GM chipset. When I built the froyo-next branch a week or two ago, it was blazing fast (although it had display error, as I described in another thread). Now, it is very jerky, like fps is limited to 15 or so, but whatever I do, all is the same speed, no matter whether it is sth. complicated or "easy" for the graphics chip.

Is this a known issue?

Stefan

[Arobase40]

OK back again,

As I said I made a complete fresh download of froyo-x86, then built
the asus_laptop target.

Same issue !!! :(

For what I have observed, sounds like mesa is switching fast to very
high resolution or to a high frequency which is beyond the scope of my
laptop screen, as the the Android logo won't show on, so I only have a
black display with a blinking cursor of the top left of the screen.

I have tried to change some parameters in Boardconfig.mk and
asus_laptop.info files but no go.

So I guess the mesa auto-detection mechanism is buggy, or at least
something is wrong in its way to work... ^^

Sorry Chih Wei, but I did nothing wrong... ^^ ;-)

On 13 avr, 08:13, Chih-Wei Huang <cwhu...@android-x86.org> wrote:
> 2011/4/13 Arobase40 <arobas...@gmail.com>:

[Chih-Wei Huang]

Hmm, check if you have these files built and
installed correctly:

/system/lib/hw/gralloc.mesa.so
/system/lib/hw/gralloc.$target.so -> gralloc.mesa.so
/system/lib/egl/egl.cfg
/system/lib/egl/libGLES_mesa.so
/system/lib/dri/i9[16]5_dri.so

2011/4/14 Arobase40 <arob...@gmail.com>:

> OK back again,
> As I said I made a complete fresh download of froyo-x86, then built
> the asus_laptop target.
>
> Same issue !!! :(
>
> For what I have observed, sounds like mesa is switching fast to very
> high resolution or to a high frequency which is beyond the scope of my
> laptop screen, as the the Android logo won't show on, so I only have a
> black display with a blinking cursor of the top left of the screen.
>
> I have tried to change some parameters in Boardconfig.mk and
> asus_laptop.info files but no go.
>
> So I guess the mesa auto-detection mechanism is buggy, or at least
> something is wrong in its way to work... ^^
>
> Sorry Chih Wei, but I did nothing wrong... ^^ ;-)

--

[Arobase40]

Yep !

All mentioned files are in their appropriate places... ^^

On 14 avr, 08:15, Chih-Wei Huang <cwhu...@android-x86.org> wrote:
> Hmm, check if you have these files built and
> installed correctly:
>
> /system/lib/hw/gralloc.mesa.so
> /system/lib/hw/gralloc.$target.so -> gralloc.mesa.so
> /system/lib/egl/egl.cfg
> /system/lib/egl/libGLES_mesa.so
> /system/lib/dri/i9[16]5_dri.so
>

> 2011/4/14 Arobase40 <arobas...@gmail.com>:

[Chris Furlough]

Does "nomodeset" on the kernel line help?

[Arobase40]

Nope !!! :(

[Arobase40]

Have you got a functionnal iso with this build id (FRG83G) ???

On 14 avr, 15:51, Chris Furlough <chrisfurlo...@gmail.com> wrote:

[Chris Furlough]

This is the point where I plead ignorance, and ask "Uhhh.  How do I check the build id?" :-)

[Arobase40]

When you lunch a build process it first show you a screen with the
caracteristics of the build.

When the iso is running, you just have to go into the Parameters and
About the phone or device... ;-)