Builds for the InFocus tablet?

[Stefan Arentz]

Do we have builds for the tablet that have a more tablet-ey UI? It looks like the builds that shipped on the tablet are for the phone and simply scaled up.

Is there documentation on how to build and install our own builds for this device?

S.

[Naoki Hirata]

As far as I know it is the same process as building b2g in general. You would need to extract the files and build your own backup folder.

The main difference is the gaia portion which is documented here :
https://wiki.mozilla.org/B2G/QA/Tips_And_Tricks#Tablet ( which I sited the URL where I got the info from )

It's been a while since I have updated it so it might be out of date.

Regards,
Naoki

> _______________________________________________
> dev-b2g mailing list
> dev...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-b2g

[Asa Dotzler]

https://wiki.mozilla.org/FirefoxOS/TCP/Patching

You will find other Flatfish contributors in #TCP on IRC and more docs
one level up from the link I gave here.

- A

[Naoki Hirata]

Thanks Asa.

Do you know if we're going to get images from the vendor themselves?
I'm asking because I think if they update the gonk, we might not get it since we have to extract the gonk from the device…
I could be wrong.

Regards,
Naoki

On May 21, 2014, at 11:16 AM, Asa Dotzler <a...@mozilla.com> wrote:

> On 5/21/14, 9:35 AM, Stefan Arentz wrote:
>>

> https://wiki.mozilla.org/FirefoxOS/TCP/Patching
>
> You will find other Flatfish contributors in #TCP on IRC and more docs one level up from the link I gave here.
>
> - A

[Asa Dotzler]

On 5/21/14, 11:32 AM, Naoki Hirata wrote:
> Thanks Asa.
>
> Do you know if we're going to get images from the vendor themselves?

> I'm asking because I think if they update the gonk, we might not get it since we have to extract the gonk from the device�
> I could be wrong.

I don't think we are. Last I heard, we'll get no help from the vendor
and it's up to us to figure out how to manage without. That's not what
I'd thought when launching the program, but that's where we are.

Suggestions? How long can we get away just flashing Gaia and Gecko
before we're likely to need Gonk changes?

- A

[Naoki Hirata]

I don't know the answer to the second question currently. Being in QA, it's my tendency to worry about things of the future as it could be a roadblock.
I guess we'll find out the hard way… There's only so much we can do if we don't have the necessary gonk changes [ if/when we need them ]. GonkIntegration bugs would give you an idea of what type of things we do have the chance of running into.

A suggestion would be to create open source drivers so that we could make the whole tablet open sourced… so we don't need to rely on the vendor for gonk support.
I doubt that's a feasible suggestion though; thought I'd ask anyhow. :) Otherwise I'd need to think about it more… :|

Regards,
Naoki

On May 21, 2014, at 11:57 AM, Asa Dotzler <a...@mozilla.com> wrote:

> On 5/21/14, 11:32 AM, Naoki Hirata wrote:

>> Thanks Asa.
>>
>> Do you know if we're going to get images from the vendor themselves?
>> I'm asking because I think if they update the gonk, we might not get it since we have to extract the gonk from the device…
>> I could be wrong.
>

> I don't think we are. Last I heard, we'll get no help from the vendor and it's up to us to figure out how to manage without. That's not what I'd thought when launching the program, but that's where we are.
>
> Suggestions? How long can we get away just flashing Gaia and Gecko before we're likely to need Gonk changes?
>

[Naoki Hirata]

Maybe someone else has a better idea? :)

On May 21, 2014, at 12:20 PM, Naoki Hirata <nhi...@mozilla.com> wrote:

> I don't know the answer to the second question currently. Being in QA, it's my tendency to worry about things of the future as it could be a roadblock.
> I guess we'll find out the hard way… There's only so much we can do if we don't have the necessary gonk changes [ if/when we need them ]. GonkIntegration bugs would give you an idea of what type of things we do have the chance of running into.
>
> A suggestion would be to create open source drivers so that we could make the whole tablet open sourced… so we don't need to rely on the vendor for gonk support.
> I doubt that's a feasible suggestion though; thought I'd ask anyhow. :) Otherwise I'd need to think about it more… :|
>

> Regards,
> Naoki
>

> On May 21, 2014, at 11:57 AM, Asa Dotzler <a...@mozilla.com> wrote:
>
>> On 5/21/14, 11:32 AM, Naoki Hirata wrote:

>>> Thanks Asa.
>>>
>>> Do you know if we're going to get images from the vendor themselves?
>>> I'm asking because I think if they update the gonk, we might not get it since we have to extract the gonk from the device…
>>> I could be wrong.
>>

>> I don't think we are. Last I heard, we'll get no help from the vendor and it's up to us to figure out how to manage without. That's not what I'd thought when launching the program, but that's where we are.
>>
>> Suggestions? How long can we get away just flashing Gaia and Gecko before we're likely to need Gonk changes?
>>

[Stefan Arentz]

I don't understand the 'we have to extract Gonk from the device' part.

Why can't I build and flash the whole thing (gonk & gaia)? Like I've been doing with the Unagi.

Is this about binary blobs again? Our build scripts extract those as part of the build, no?

Sorry if I sound like a noob but I have not looked at any of this in a while :-/

S.

----- Original Message -----
> Maybe someone else has a better idea? :)
>
> On May 21, 2014, at 12:20 PM, Naoki Hirata <nhi...@mozilla.com> wrote:
>
> > I don't know the answer to the second question currently. Being in QA,
> > it's my tendency to worry about things of the future as it could be a
> > roadblock.
> > I guess we'll find out the hard way… There's only so much we can do if we
> > don't have the necessary gonk changes [ if/when we need them ].
> > GonkIntegration bugs would give you an idea of what type of things we do
> > have the chance of running into.
> >
> > A suggestion would be to create open source drivers so that we could make
> > the whole tablet open sourced… so we don't need to rely on the vendor for
> > gonk support.
> > I doubt that's a feasible suggestion though; thought I'd ask anyhow. :)
> > Otherwise I'd need to think about it more… :|
> >

> > Regards,
> > Naoki
> >

> > On May 21, 2014, at 11:57 AM, Asa Dotzler <a...@mozilla.com> wrote:
> >
> >> On 5/21/14, 11:32 AM, Naoki Hirata wrote:

> >>> Thanks Asa.
> >>>
> >>> Do you know if we're going to get images from the vendor themselves?
> >>> I'm asking because I think if they update the gonk, we might not get it
> >>> since we have to extract the gonk from the device…
> >>> I could be wrong.
> >>

> >> I don't think we are. Last I heard, we'll get no help from the vendor and
> >> it's up to us to figure out how to manage without. That's not what I'd
> >> thought when launching the program, but that's where we are.
> >>
> >> Suggestions? How long can we get away just flashing Gaia and Gecko before
> >> we're likely to need Gonk changes?
> >>

[Stefan Arentz]

I am obviously confusing gonk and gecko here. I see I can build and flash both, so I'm a happy hacker :-)

[Naoki Hirata]

I might not be the best to explain this; I'm sure others can explain it better.

As my basic understanding goes:

Most of the drivers, libraries that interface the hardware to the software level is in the Gonk layer : see https://developer.mozilla.org/en-US/Firefox_OS/Platform/Gonk

Some of the configurations for gonk lies within the kernel as well ( boot.img )

Gecko is all software level and has APIs, the engine, etc. see https://developer.mozilla.org/en-US/Firefox_OS/Platform/Architecture .

The system.img that gets flashed with a fastboot flash contains the parts of the gonk, gecko and gaia ( if the gaia is installed to the system partition ).

There's an extract script that ends up extracting the gonk and recompiles those files with our code and creates a new boot.img, system.img
That's what the backup-<device> folder is and is the reason why you were able create the boot.img and system.img It's the product of the extract script. In some devices, like the nexus, the repo for that device is pulled from the source repo ( i.e. from Google's repo ) and that's why we don't need a backup-<device> folder for those devices. We build based on the changes from that repo.

If you have an old backup-<device> folder and not from the latest oem build, if they make changes to fix gonk level bugs; you will not get those fixes.
i.e. there are bugs that we can't necessarily fix in the gecko/gaia. Generally, I try to help releng keep those backup-<device> folders up to date so we don't have to worry about this case for QA / pvtbuilds .

Regards,
Naoki

[Juan Gómez]

As we are heading v2.0, there should be no problem with the current "Gonk" provided by the vendor. They actually don't provide Gonk at all, just some private vendor libraries and HAL implementations for Android JB (4.2.2). We use those bits with a lot of other libreries from AOSP to build Gonk, so yes, we are tied in some way to this Android base, but that's not a problem so far. I mean, as the vendor is not going to update their implementations to a newer Android base (JB 4.3 or KK 4.4), we just need to worry about keeping a good support of JB (4.2.2) in Gecko. That should be enough to stay the tablets tuned with latets Gecko/Gaia versions for a long time.

On Wed, May 21, 2014 at 10:20 PM, Naoki Hirata <nhi...@mozilla.com> wrote:

I might not be the best to explain this; I'm sure others can explain it better.

As my basic understanding goes:

Most of the drivers, libraries that interface the hardware to the software level is in the Gonk layer : see https://developer.mozilla.org/en-US/Firefox_OS/Platform/Gonk

Some of the configurations for gonk lies within the kernel as well ( boot.img )

Gecko is all software level and has APIs, the engine, etc.  see https://developer.mozilla.org/en-US/Firefox_OS/Platform/Architecture .

The system.img that gets flashed with a fastboot flash contains the parts of the gonk, gecko and gaia ( if the gaia is installed to the system partition ).

There's an extract script that ends up extracting the gonk and recompiles those files with our code and creates a new boot.img, system.img
That's what the backup-<device> folder is and is the reason why you were able create the boot.img and system.img  It's the product of the extract script.  In some devices, like the nexus, the repo for that device is pulled from the source repo ( i.e. from Google's repo ) and that's why we don't need a backup-<device> folder for those devices.  We build based on the changes from that repo.

If you have an old backup-<device> folder and not from the latest oem build, if they make changes to fix gonk level bugs; you will not get those fixes.
i.e. there are bugs that we can't necessarily fix in the gecko/gaia.  Generally, I try to help releng keep those backup-<device> folders up to date so we don't have to worry about this case for QA / pvtbuilds .

Regards,
Naoki

On May 21, 2014, at 12:35 PM, Stefan Arentz <sar...@mozilla.com> wrote:

> I am obviously confusing gonk and gecko here. I see I can build and flash both, so I'm a happy hacker :-)
>
> S.
>
> ----- Original Message -----
>> I don't understand the 'we have to extract Gonk from the device' part.
>>
>> Why can't I build and flash the whole thing (gonk & gaia)? Like I've been
>> doing with the Unagi.
>>
>> Is this about binary blobs again? Our build scripts extract those as part of
>> the build, no?
>>
>> Sorry if I sound like a noob but I have not looked at any of this in a while
>> :-/

[Joe Cheng]

Gonk shouldn’t need to be updated frequently but we still need to figure out how to get the infrequent Gonk updates from our partner to everyone (once every now and then)

Then it sounds like as long as Gecko/Gaia can be flashed easily to the tablets, we should have happy tablet hackers

Re,

Joe Cheng

——————————
Mozilla Corp.

jch...@mozilla.com

On May 22, 2014, at 5:11 PM, Juan Gómez <ati...@gmail.com> wrote:

As we are heading v2.0, there should be no problem with the current "Gonk" provided by the vendor. They actually don't provide Gonk at all, just some private vendor libraries and HAL implementations for Android JB (4.2.2). We use those bits with a lot of other libreries from AOSP to build Gonk, so yes, we are tied in some way to this Android base, but that's not a problem so far. I mean, as the vendor is not going to update their implementations to a newer Android base (JB 4.3 or KK 4.4), we just need to worry about keeping a good support of JB (4.2.2) in Gecko. That should be enough to stay the tablets tuned with latets Gecko/Gaia versions for a long time.

On Wed, May 21, 2014 at 10:20 PM, Naoki Hirata <nhi...@mozilla.com> wrote:

I might not be the best to explain this; I'm sure others can explain it better.

As my basic understanding goes:

Most of the drivers, libraries that interface the hardware to the software level is in the Gonk layer : see https://developer.mozilla.org/en-US/Firefox_OS/Platform/Gonk

Some of the configurations for gonk lies within the kernel as well ( boot.img )

Gecko is all software level and has APIs, the engine, etc.  see https://developer.mozilla.org/en-US/Firefox_OS/Platform/Architecture .

The system.img that gets flashed with a fastboot flash contains the parts of the gonk, gecko and gaia ( if the gaia is installed to the system partition ).

There's an extract script that ends up extracting the gonk and recompiles those files with our code and creates a new boot.img, system.img
That's what the backup-<device> folder is and is the reason why you were able create the boot.img and system.img  It's the product of the extract script.  In some devices, like the nexus, the repo for that device is pulled from the source repo ( i.e. from Google's repo ) and that's why we don't need a backup-<device> folder for those devices.  We build based on the changes from that repo.

If you have an old backup-<device> folder and not from the latest oem build, if they make changes to fix gonk level bugs; you will not get those fixes.
i.e. there are bugs that we can't necessarily fix in the gecko/gaia.  Generally, I try to help releng keep those backup-<device> folders up to date so we don't have to worry about this case for QA / pvtbuilds .

Regards,
Naoki

On May 21, 2014, at 12:35 PM, Stefan Arentz <sar...@mozilla.com> wrote:

> I am obviously confusing gonk and gecko here. I see I can build and flash both, so I'm a happy hacker :-)
>
> S.
>
> ----- Original Message -----
>> I don't understand the 'we have to extract Gonk from the device' part.
>>
>> Why can't I build and flash the whole thing (gonk & gaia)? Like I've been
>> doing with the Unagi.
>>
>> Is this about binary blobs again? Our build scripts extract those as part of
>> the build, no?
>>
>> Sorry if I sound like a noob but I have not looked at any of this in a while
>> :-/

_______________________________________________
dev-b2g mailing list
dev...@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-b2g