On 29/04/2021 20:34, Christos Zoulas wrote:
Some ext4 features were implemented as part of GSoC 2016 (extents,
htrees).
I am sure that there are other unimplemented features. What are you looking
for?
christos
I'd like to have full ext4 support so an ext4-formatted disk could be
used to e
Hi,
I use both Linux and NetBSD, so I would be interested in implementing
ext4 support.
However, the project description page at
https://wiki.netbsd.org/projects/project/ext4fs/
is 6 years old and I wonder whether its status has changed since then.
Vincent
Hi,
how about you tried this patch? Among quite a few other changes, I need
to remove AWIN_GMAC_MAC_INT_RGSMII from the default mask to make the
awge0 on my DE0 nano-soc work (at Gbps speed, and because the PHY there
is connected via RGMII). It looks like the media changing code is
present but we
Hi,
David Holland writes:
> If, however, you use a base year that's off by 30 when programming it,
> it won't be wrong in 2100, it will be wrong *now* -- it is 2016 so if
> you loaded the time using a base year of 1970 when the clock actually
> expected 2000, it will think it's 2046 (not a leap
Hi,
in order to avoid breaking working setups using a dsrtc at iic, I
introduced a flag DSRTC_FLAG_YEAR_START_2K to impose a base year of 2000
on a per-chip basis. The existing code starts at POSIX_BASE_YEAR (1970),
with the comment:
/* XXX: Should be an MD way to specify EPOCH used by BIOS/Firm
Matt Thomas writes:
> A lot of systems are coming with compute/peripheral processors with
> limited ram, etc.
>
> I was wondering what the abstraction should be?
>
> Obviously, mmap()'ing their memory would be nice. But what about
> stopping/starting? Messaging?
How about using/extending the
Warner Losh writes:
> On Sep 5, 2012, at 12:43 AM, Jukka Marin wrote:
>
>> The main features of our current hardware are:
>> - AT91SAM9G20 MCU (400 MHz)
>> [...]
>
> Apart from a few clocks, this should work with the AT91SAM9260 support
> that's in the tree. The device tables/trees are the same,
