On Wed, 16 Aug 2017, Chris Brandt wrote:
> I made an example once were all the graphics were RAW and uncompressed
> and marked as XIP in AXFS. The result was a large saving of RAM because
> as the graphics framework (DirectFB) would copy directly from Flash
> whenever it needed to do a backgrou
On Wednesday, August 16, 2017 1, Nicolas Pitre wrote:
> > Just FYI,
> > I'm running an xipImage with all the RZ/A1 upstream drivers enabled and
> > only using about 4.5MB of total system RAM.
> > That's pretty good. Of course for a real application, you would trim off
> > the drivers and subsystems
On Wed, 16 Aug 2017, Chris Brandt wrote:
> On Wednesday, August 16, 2017, Nicolas Pitre wrote:
> > > Yes, now I can boot with my rootfs being a XIP cramfs.
> > >
> > > However, like you said, libc is not XIP.
> >
> > I think I have it working now. Probably learned more about the memory
> > manage
On Wednesday, August 16, 2017, Nicolas Pitre wrote:
> > Yes, now I can boot with my rootfs being a XIP cramfs.
> >
> > However, like you said, libc is not XIP.
>
> I think I have it working now. Probably learned more about the memory
> management internals than I ever wanted to know. Please try th
On Tue, 15 Aug 2017, Chris Brandt wrote:
> On Tuesday, August 15, 2017 1, Nicolas Pitre wrote:
> > I was able to reproduce. The following patch on top should partially fix
> > it. I'm trying to figure out how to split a vma and link it properly in
> > the case the vma cannot be mapped entirely. I
On Tuesday, August 15, 2017 1, Nicolas Pitre wrote:
> I was able to reproduce. The following patch on top should partially fix
> it. I'm trying to figure out how to split a vma and link it properly in
> the case the vma cannot be mapped entirely. In the mean time shared libs
> won't be XIP.
>
>
On Mon, 14 Aug 2017, Chris Brandt wrote:
> On Monday, August 14, 2017, Nicolas Pitre wrote:
> > > However, now with your mkcramfs tool, I can no longer mount my cramfs
> > > image as the rootfs on boot. I was able to do that before (ie, 30
> > minutes
> > > ago) when using the community mkcramfs (
On Monday, August 14, 2017, Nicolas Pitre wrote:
> > However, now with your mkcramfs tool, I can no longer mount my cramfs
> > image as the rootfs on boot. I was able to do that before (ie, 30
> minutes
> > ago) when using the community mkcramfs (ie, 30 minutes ago).
> >
> > I get this:
> >
> > [
On Mon, 14 Aug 2017, Chris Brandt wrote:
> On Monday, August 14, 2017, Nicolas Pitre wrote:
> > > I just applied the patches tried this simple test:
> > > - tested with a Renesas RZ/A1 (Cortex-A9...so it has an MMU).
> > > - I set the sticky bit for busybox before using mkcramfs
> >
> > You nee
On Monday, August 14, 2017, Nicolas Pitre wrote:
> > I just applied the patches tried this simple test:
> > - tested with a Renesas RZ/A1 (Cortex-A9...so it has an MMU).
> > - I set the sticky bit for busybox before using mkcramfs
>
> You need the newer mkcramfs I linked to in the documentation.
On Mon, 14 Aug 2017, Chris Brandt wrote:
> On Friday, August 11, 2017, Nicolas Pitre wrote:
> > This series brings a nice refresh to the cramfs filesystem, adding the
> > following capabilities:
> >
> > - Direct memory access, bypassing the block and/or MTD layers entirely.
> >
> > - Ability to
On Friday, August 11, 2017, Nicolas Pitre wrote:
> This series brings a nice refresh to the cramfs filesystem, adding the
> following capabilities:
>
> - Direct memory access, bypassing the block and/or MTD layers entirely.
>
> - Ability to store individual data blocks uncompressed.
>
> - Abilit
This series brings a nice refresh to the cramfs filesystem, adding the
following capabilities:
- Direct memory access, bypassing the block and/or MTD layers entirely.
- Ability to store individual data blocks uncompressed.
- Ability to locate individual data blocks anywhere in the filesystem.
T
13 matches
Mail list logo
