Unlike the TI sitara/OMAP boot rom the raspberry pi boot rom
will fail to read FAT12, the filesystem must be FAT16 or FAT32.
These changes require the raspberrypi-firmware port sent to ports@
to build release along with u-boot-aarch64.
Index: distrib/arm64/miniroot/Makefile
==
On Wed, Feb 01, 2017 at 10:09:14PM +1100, Jonathan Gray wrote:
> On Mon, Jan 30, 2017 at 07:28:03PM +0100, Stefan Kempf wrote:
> > Jonathan Gray wrote:
> > > Base gcc4 changes the defaults to set -Wno-pointer-sign.
> > > Base clang does not, I'm not sure where in the llvm code to do so.
> > > Base
Currently, we do not have a way to iterate over child FDT nodes, which
is a problem when you have a devices like the USB system on the am335x
(Beaglebone Black):
https://uglyman.kremlin.cc/gitweb/gitweb.cgi?p=bbb-usb.git;a=blob;f=misc/fdt/am335x-boneblack.dts;h=8799dc1d171961d3cd9a941131a82a15bbe4
On Sun, Feb 05, 2017 at 04:51:50PM -0800, Philip Guenther wrote:
> On Sun, 5 Feb 2017, Ossi Herrala wrote:
> > init(8) is wanted to have process ID 1. It's also the only process which
> > is assigned non-random PID (well, there's also swapper as PID 0).
> >
> > This patch renames fork1() to fork1_t
On Mon, 6 Feb 2017, Robert Klein wrote:
> TL;DR: OpenBSD's ldapd(8) has issues when deleting individual attribute
> values. Patch below.
I've committed it with some whitespace and comment style tweaks. Thanks
for poking on this again!
Philip Guenther
On 2017-02-06, Martin Pieuchot wrote:
> guenther@ pointed out during a2k17 that nfsrv_rcv() already has a way to
> not re-enter the socket layer. Instead of doing soreceive() directly in
> the receiving path, we notify and wakeup nfsd(8) to do it.
>
> I'd like to do that unconditionally to fix o
On Sat, 11 Feb 2017 01:29:08 -0800, Philip Guenther wrote:
> To simplify the filedesc fd_ofileflags handling, how about if we make
> falloc() take optional flags to OR into the new fd's ofileflags? That
> eliminates a quarter of the references to fd_ofileflags.
OK, this seems much better than f
>I'm not sure if you choose DVACT_WAKEUP on purpose, another way of doing
>it would be to do a task_add() in DVACT_RESUME. The difference is that
>the resuming thread is not allowed to sleep in RESUME. At some point we
>tried to keep the number of WAKEUP low, but I'm not sure if it is still
>rele
On Sat, Feb 11, 2017 at 10:31:39AM +, Peter Kay wrote:
>
>
> On Thu, Jan 26, 2017 at 10:38:44AM +0100, Stefan Sperling wrote:
> > On Thu, Jan 26, 2017 at 06:36:06AM +, Peter Kay wrote:
> > > sfer overflow
> >
> > Interesting. This is the first time I've ever seen this panic trigger.
> >
On Thu, Jan 26, 2017 at 10:38:44AM +0100, Stefan Sperling wrote:
> On Thu, Jan 26, 2017 at 06:36:06AM +, Peter Kay wrote:
> > sfer overflow
>
> Interesting. This is the first time I've ever seen this panic trigger.
>
> Can you apply this patch and try to trigger it again?
I've been running
To simplify the filedesc fd_ofileflags handling, how about if we make
falloc() take optional flags to OR into the new fd's ofileflags? That
eliminates a quarter of the references to fd_ofileflags.
While here, make falloc() assert that its return arguments are non-NULL,
as it doesn't make sense
11 matches
Mail list logo