On Fri, 2013-07-19 at 11:31 +1000, Jonathan Liu wrote:
> Hi Robert,
>
> I tested your patches with my ext4 image on Intel Atom D2500HN board
> and it is working well.
> Previously I have been using custom image class which requires root
> privileges as I need to be able to specify custom options t
Hi Robert,
I tested your patches with my ext4 image on Intel Atom D2500HN board
and it is working well.
Previously I have been using custom image class which requires root
privileges as I need to be able to specify custom options to mkfs.ext4
which are not available with genext2fs and cannot be se
On 07/18/2013 09:13 PM, Jonathan Liu wrote:
On 18/07/2013 10:32 PM, Robert Yang wrote:
On 07/06/2013 10:49 PM, Jonathan Liu wrote:
Any updates?
Hi Jonathan,
I've updated the patches, now they are working well, the "fsck -fn" finds
no errors any more, but I have to send the patches to the
On 18/07/2013 10:32 PM, Robert Yang wrote:
On 07/06/2013 10:49 PM, Jonathan Liu wrote:
Any updates?
Hi Jonathan,
I've updated the patches, now they are working well, the "fsck -fn" finds
no errors any more, but I have to send the patches to the ext4 mailing
list
firstly, you can try it if
On 07/06/2013 10:49 PM, Jonathan Liu wrote:
Any updates?
Hi Jonathan,
I've updated the patches, now they are working well, the "fsck -fn" finds
no errors any more, but I have to send the patches to the ext4 mailing list
firstly, you can try it if you are interested in it atm.:
git://git.p
On 07/06/2013 10:49 PM, Jonathan Liu wrote:
On 14/05/2013 3:32 PM, Robert Yang wrote:
On 05/13/2013 09:22 PM, Jonathan Liu wrote:
On 13/05/2013 8:50 PM, Robert Yang wrote:
On 05/13/2013 05:50 PM, Jonathan Liu wrote:
On 13/05/2013 7:23 PM, Robert Yang wrote:
Hi Jonathan Liu,
What's yo
On 14/05/2013 3:32 PM, Robert Yang wrote:
On 05/13/2013 09:22 PM, Jonathan Liu wrote:
On 13/05/2013 8:50 PM, Robert Yang wrote:
On 05/13/2013 05:50 PM, Jonathan Liu wrote:
On 13/05/2013 7:23 PM, Robert Yang wrote:
Hi Jonathan Liu,
What's your configuration, please, I tried a core-image-
On 05/13/2013 09:22 PM, Jonathan Liu wrote:
On 13/05/2013 8:50 PM, Robert Yang wrote:
On 05/13/2013 05:50 PM, Jonathan Liu wrote:
On 13/05/2013 7:23 PM, Robert Yang wrote:
Hi Jonathan Liu,
What's your configuration, please, I tried a core-image-minimal building
just now, didn't notice th
On 13/05/2013 8:50 PM, Robert Yang wrote:
On 05/13/2013 05:50 PM, Jonathan Liu wrote:
On 13/05/2013 7:23 PM, Robert Yang wrote:
Hi Jonathan Liu,
What's your configuration, please, I tried a core-image-minimal
building
just now, didn't notice this error. Did the error come after these
patc
On 05/13/2013 05:50 PM, Jonathan Liu wrote:
On 13/05/2013 7:23 PM, Robert Yang wrote:
Hi Jonathan Liu,
What's your configuration, please, I tried a core-image-minimal building
just now, didn't notice this error. Did the error come after these patches
applied ?
Yes, the errors occured after
On 13/05/2013 7:23 PM, Robert Yang wrote:
Hi Jonathan Liu,
What's your configuration, please, I tried a core-image-minimal building
just now, didn't notice this error. Did the error come after these
patches
applied ?
Yes, the errors occured after applying your patches.
distro conf:
DISTRO_F
Hi Jonathan Liu,
What's your configuration, please, I tried a core-image-minimal building
just now, didn't notice this error. Did the error come after these patches
applied ?
My configuration:
MACHINE = "qemux86"
IMAGE_FSTYPES += "ext4"
// Robert
On 05/13/2013 12:59 PM, Jonathan Liu wrote:
H
Hi Robert,
I get the following errors doing filesystem check on the ext4 image:
# fsck.ext4 -fn tmp/deploy/images/custom-image-custom.ext4.ext4
e2fsck 1.42.7 (21-Jan-2013)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Entry 'mtd7' in /dev (2739) has an incorrect
On 05/08/2013 03:51 PM, Darren Hart wrote:
On 05/08/2013 12:48 AM, Robert Yang wrote:
On 05/08/2013 03:39 PM, Darren Hart wrote:
Always discuss them upstream first. If they are accepted upstream, THEN,
we can roll them into oe-core if we don't want to bring in everything
that landed before
On 05/08/2013 12:48 AM, Robert Yang wrote:
>
>
> On 05/08/2013 03:39 PM, Darren Hart wrote:
>> Always discuss them upstream first. If they are accepted upstream, THEN,
>> we can roll them into oe-core if we don't want to bring in everything
>> that landed before them too. But always discuss chang
On 05/08/2013 03:39 PM, Darren Hart wrote:
Always discuss them upstream first. If they are accepted upstream, THEN,
we can roll them into oe-core if we don't want to bring in everything
that landed before them too. But always discuss changes to a project to
the project before doing so in oe-cor
Always discuss them upstream first. If they are accepted upstream, THEN,
we can roll them into oe-core if we don't want to bring in everything
that landed before them too. But always discuss changes to a project to
the project before doing so in oe-core.
Thanks,
Darren
On 05/07/2013 06:49 PM, Ro
Hi Darren,
No, I haven't sent them to the ext mailing list, can we merge them in
oe-core and then back port to the ext community ? Or I should send them
to the ext mailing list first ?
// Robert
On 05/08/2013 06:48 AM, Darren Hart wrote:
Have these been reviewed on the ext mailing list alread
Have these been reviewed on the ext mailing list already?
--
Darren
On 05/07/2013 02:48 AM, Robert Yang wrote:
> * The benefits:
> - Really support ext4
> - Support the sparse file (the sparse file became into the common file
> before)
> - Have a uniform code for ext2/3/4 generation
> -
* The benefits:
- Really support ext4
- Support the sparse file (the sparse file became into the common file before)
- Have a uniform code for ext2/3/4 generation
- Remove the depends on genext2fs-native
* Impact
- Build time:
a) If we build fresh core-image-sato, there is nearly no
20 matches
Mail list logo
