Re: copyinstr and ENAMETOOLONG

2016-12-02 Thread Eric van Gyzen
On 11/02/2016 15:33, Jilles Tjoelker wrote: > On Wed, Nov 02, 2016 at 02:24:43PM -0500, Eric van Gyzen wrote: >> Does copyinstr guarantee that it has filled the output buffer when it >> returns ENAMETOOLONG? I usually try to answer my own questions, but I >> don't speak many dialects of assembly.

CFT EFI Boot Refactoring

2016-12-02 Thread Eric McCorkle
Hello everyone, My work to refactor the EFI boot loader has been in review for some time now. This work is a behavior-neutral refactoring which eliminates duplicated code in boot1, provides better integration of boot1 and loader with the EFI API, and moves towards better compliance with the recom

QLogic FastLinQ support

2016-12-02 Thread Slawa Olhovchenkov
Is support for QLogic FastLinQ QL45000 planed in FreeBSD? ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: copyinstr and ENAMETOOLONG

2016-12-02 Thread Jilles Tjoelker
On Fri, Dec 02, 2016 at 10:20:32AM -0600, Eric van Gyzen wrote: > On 11/02/2016 15:33, Jilles Tjoelker wrote: > > On Wed, Nov 02, 2016 at 02:24:43PM -0500, Eric van Gyzen wrote: > >> Does copyinstr guarantee that it has filled the output buffer when it > >> returns ENAMETOOLONG? I usually try to a

Re: CFT EFI Boot Refactoring

2016-12-02 Thread Ben Woods
On 3 December 2016 at 14:40, Ben Woods wrote: > I just applied your diff to my subversion repository, and tried to > buildworld, but the build failed with the following error: > > make[6]: make[6]: don't know how to make efipart.c. Stop > > make[6]: stopped in /usr/src/sys/boot/efi/drivers > ***