On Tue, Feb 11, 2020 at 9:10 PM Florian Weimer wrote:
> * Ansgar:
> > Arnd Bergmann writes:
> >> On Mon, Feb 10, 2020 at 11:16 PM Florian Weimer wrote:
> >>> There's going to be a _TIME_BITS selector, similar to
> >>> _FILE_OFFSET_BITS.
> >>>
> >>> There was a proposal to have only one API
* Ansgar:
> Arnd Bergmann writes:
>> On Mon, Feb 10, 2020 at 11:16 PM Florian Weimer wrote:
>>> There's going to be a _TIME_BITS selector, similar to
>>> _FILE_OFFSET_BITS.
>>>
>>> There was a proposal to have only one API before, but I think the
>>> agreement was that it wouldn't save much
On Tue, Feb 11, 2020 at 12:07 PM Marco d'Itri wrote:
>
> On Feb 11, Arnd Bergmann wrote:
>
> > I agree that changing the i386 port is probably a bad idea at the moment,
> > let's see how the armhf port turns out and fix all the bugs first, as this
> > is clearly needed anyway. Once there is a
On Tue, Feb 11, 2020 at 12:01:28PM +0100, Marco d'Itri wrote:
>On Feb 11, Arnd Bergmann wrote:
>
>> I agree that changing the i386 port is probably a bad idea at the moment,
>> let's see how the armhf port turns out and fix all the bugs first, as this
>> is clearly needed anyway. Once there is a
Quoting Dominique Dumont (2020-02-11 14:16:22)
> On Tuesday, 11 February 2020 12:13:23 CET Dominique Dumont wrote:
> > I'll search in u-boot archive for other threads
>
> This is promising:
>
> https://lists.denx.de/pipermail/u-boot/2016-March/249735.html
I suspect that addresses only the issue
On Tuesday, 11 February 2020 12:13:23 CET Dominique Dumont wrote:
> I'll search in u-boot archive for other threads
This is promising:
https://lists.denx.de/pipermail/u-boot/2016-March/249735.html
On Tuesday, 11 February 2020 12:23:06 CET Jonas Smedegaard wrote:
> someone (you, Dominique?) should test
> also against the "original" LIME2 rev. C or older, to ensure there is no
> regression there!
I don't have any other Lime2 board.
All the best
Quoting Dominique Dumont (2020-02-11 12:13:23)
> On Monday, 10 February 2020 03:39:39 CET Vagrant Cascadian wrote:
> > Please submit a patch to upstream fixing this in the appropriate
> > files in configs/*; I'd guess
> > configs/A20-OLinuXino-Lime2-eMMC_defconfig and/or
> >
On Monday, 10 February 2020 03:39:39 CET Vagrant Cascadian wrote:
> Please submit a patch to upstream fixing this in the appropriate files
> in configs/*; I'd guess configs/A20-OLinuXino-Lime2-eMMC_defconfig
> and/or configs/A20-OLinuXino-Lime2_defconfig.
It looks like a similar patches was
On Feb 11, Arnd Bergmann wrote:
> I agree that changing the i386 port is probably a bad idea at the moment,
> let's see how the armhf port turns out and fix all the bugs first, as this
> is clearly needed anyway. Once there is a working armhf version with
> full time64 user space, there can be a
Arnd Bergmann writes:
> On Mon, Feb 10, 2020 at 11:16 PM Florian Weimer wrote:
>> There's going to be a _TIME_BITS selector, similar to
>> _FILE_OFFSET_BITS.
>>
>> There was a proposal to have only one API before, but I think the
>> agreement was that it wouldn't save much complexity.
>
> It
On Fri, Feb 7, 2020 at 10:21 PM Florian Weimer wrote:
>
> * Steve McIntyre:
>
> > The kernel is *basically* fixed now. Internally, data structures
> > should now be safe. There are a small number places where 32-bit time
> > is still a thing, but it's in hand. A number of syscalls, ioctls,
> >
On Mon, Feb 10, 2020 at 11:16 PM Florian Weimer wrote:
>
> * Ben Hutchings:
>
> > On Sun, 2020-02-09 at 11:57 +0100, Florian Weimer wrote:
> >> * Ben Hutchings:
> >>
> >> > If I recall correctly, glibc *will* provide both entry points, so there
> >> > is no ABI break. But the size of time_t
13 matches
Mail list logo
