Nicolas Martyanoff | 30 Mar 11:33 2015
Picon

Intel HD 5500 driver port

Hi,

I have trouble finding info about support for the Intel HD 5500 graphic chip
(used on broadwell platforms such as new Thinkpads) on FreeBSD. On Linux, it
seems to be supported by the Intel driver Since June 2014¹.

Is there a port in progress, or some development being done ?

Feel free to redirect me to another mailing list if this is not the correct
one :)

Thank you in advance.

[1] https://01.org/linuxgraphics/downloads/2014/2014q2-intel-graphics-stack-release

--

-- 
Nicolas Martyanoff
http://wandrian.net
khaelin <at> gmail.com
_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"

Eric McCorkle | 30 Mar 02:45 2015
Picon

ZFS support for EFI

Hi folks,

I've been messing around off and on for a while with adding ZFS support
to the EFI boot.  It's been mostly exploratory and self-contained up to
this point, but I've gotten to a point that warrants some discussion.

First, I've converted boot1.c (the EFI boot block) to use an FS module
framework.  This facilitates the addition of ZFS, and should also come
in handy if someone wants to add other functionality later (ie. crypto,
netboot, etc.)

More importantly, the EFI loader doesn't seem to make use of its
command-line arguments at all.  But a ZFS-enabled loader would really
need the ability to take arguments from boot1 (or grub, or whatever
else).  On the boot1 side, with ZFS you need to load and parse
/boot/loader.conf (which may cause you to switch pools), then hand off
the information to loader.  In the BIOS loader, that's done through a
binary data object that gets passed in.  Command-line strings seem like
the most sensible way to do it with EFI.

Would this be the right way to go, and if so, what ought these
command-line strings look like?

Thanks,
Eric
_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"

(Continue reading)

Picon

Export docs to EPUB project idea - any takers yet?

Hi,

I've posted this earlier to freebsd-doc <at>  but I am re-posting it here. I've
been looking through project ideas as I want to start participating in
FreeBSD development. I found the export to EPUB idea, and I thought this
would be a good project to take.

I wonder if anyone has started working on this project idea. If not, could
anyone enlighten me as to how I get started working on the idea please.

Thanks!
_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"

Slawa Olhovchenkov | 28 Mar 12:20 2015
Picon

irq cpu binding

Can someone describe how on FreeBSD/amd64 do interrupt handling?
Can be interrupt handler (hardware interrupt) direct dispatch to
specific CPU core (and only to this core)?
Can be all work be only on this core (ithread, device driver interrupt
handler, finalise)?
_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"

Alexander Motin | 27 Mar 21:57 2015
Picon

MAXBSIZE increase

Hi.

Experimenting with NFS and ZFS I found an inter-operation issue: ZFS by
default uses block of 128KB, while FreeBSD NFS (both client and server)
is limited to 64KB requests by the value of MAXBSIZE. On file rewrite
that limitation makes ZFS to do slow read-modify-write cycles for every
write operation, instead of just writing the new data.  Trivial iozone
test show major difference between initial write and rewrite speeds
because of this issue.

Looking through the sources I've found and in r280347 fixed number of
improper MAXBSIZE use cases in device drivers. After that I see no any
reason why MAXBSIZE can not be increased to at least 128KB to match ZFS
default (ZFS now supports block up to 1MB, but that is not default and
so far rare). I've made a test build and also successfully created UFS
file system with 128KB block -- not sure it is needed, but seems it
survives this change well too.

Is there anything I am missing, or it is safe to rise this limit now?

--

-- 
Alexander Motin
_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"

rank1seeker | 27 Mar 20:13 2015
Picon

Port's make knobs in DESTDIR

# make VAR_EXISTING_IN_PORTS_MAKEFILE=value install clean
    OK => Overrides port's var from Makefile with value

# make VAR_EXISTING_IN_PORTS_MAKEFILE=value DESTDIR=/path/ install clean
    FAIL => Fails to override port's var from Makefile when DESTDIR is
    set

Why is it so?

Domagoj S.
_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"

rank1seeker | 27 Mar 15:20 2015
Picon

ports-mgmt/pkg (still) fails to install in DESTDIR

# make -C /usr/ports/ports-mgmt/pkg DESTDIR=/poligon/freebsd install clean
Fails at:
------------------
====> Compressing man pages (compress-man)
===>  Installing for pkg-1.4.12
===>  Checking if pkg already installed
===>   Registering installation for pkg-1.4.12
pkg-static: Cannot open "/var/run/ld-elf.so.hints": No such file or directory
*** Error code 1

Stop.
make[1]: stopped in /tmp/mountpoint.w4WP0q/ports-mgmt/pkg
*** Error code 1

Stop.
make: stopped in /tmp/mountpoint.w4WP0q/ports-mgmt/pkg
===>  Chrooted make in /poligon/freebsd failed
===>  Cleaning up...
*** Error code 1

Stop.
make: stopped in /usr/ports/ports-mgmt/pkg
------------------

I've found this, but it was 2 years ago and still not implemented/fixed:
    http://lists.freebsd.org/pipermail/svn-src-stable-10/2013-December/000495.html

My fix vas to chroot in DESTDIR and simply issue:
# pkg -v
Which started bootstrapp ...
(Continue reading)

Edward Tomasz Napierała | 27 Mar 13:40 2015
Picon

Linux core under FreeBSD.

Is there a way to debug a core generated by Linux process running
under Linuxulator on 11-CURRENT?  Thanks!

_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"

Wojciech Puchar | 27 Mar 09:32 2015
Picon

FreeBSD/cubieboard (to be exact - banana pi)

is there any progress on it?

i found ahci, ethernet and mmc commented out in CUBIEBOARD2 in both 
FreeBSD-10 and current.

NetBSD seems to support it completely but for many reasons i would prefer 
FreeBSD working on it.
_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"

Wojciech Puchar | 26 Mar 11:26 2015
Picon

Seagate Archive HDD

http://www.storagereview.com/seagate_archive_hdd_review_8tb

i want to buy 2 such drives for backup server.

This drives use shingled recording.

Are anyone using them and can confirm they are compatible on software 
level with other disks? I understand average random write time would be 
5-10 times slower than normal drive because of the need of rewrite few 
full tracks worth of data, but otherwise will then be compatible and can i 
use it as usual?
_______________________________________________
freebsd-hackers <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe <at> freebsd.org"

Stefan Grundmann | 25 Mar 10:03 2015

trusted gptboot preview [patch]

hi, the promised minimal howto got a bit longer than planed.

best regards

Stefan Grundmann

--------------------------------------------------------------------------

SRTM (Static Root Of Trust) FreeBSD boot

* Motivation

 Anti Evil Maid
 http://theinvisiblethings.blogspot.de/2011/09/anti-evil-maid.html

* Existing SRTM solutions

** TrustedGRUB
 - http://trustedgrub.sourceforge.net/
 - ported by BSSSD
 - GNU GRUB 1.* based
 - no GPT support
 - insufficient UFS support
 - no easy way to decrypt disk keys with secrets from TPM

** GRUB-IMA
 - http://sourceforge.net/projects/trousers/files/Grub-IMA/
 - same limitations as TrustedGRUB plus never ported to FreeBSD

* Deliverables
(Continue reading)


Gmane