Re: sa(4) driver changes available for test

2015-03-07 Thread Harald Schmalzbauer
 Bezüglich Kenneth D. Merry's Nachricht vom 19.02.2015 01:13 (localtime):
 I have updated the patches.

 I have removed the XPT_DEV_ADVINFO changes from the patches to head, since
 I committed those separately.

 I have (hopefully) fixed the build for the stable/10 patches by MFCing
 dependencies.  (One of them mav did for me, thanks!)

 Rough draft commit message:

 http://people.freebsd.org/~ken/sa_changes_commitmsg.20150218.1.txt

 The patches against FreeBSD/head as of SVN revision 278975:

 http://people.freebsd.org/~ken/sa_changes.20150218.1.txt

 And (untested) patches against FreeBSD stable/10 as of SVN revision 278974:

 http://people.freebsd.org/~ken/sa_changes.stable_10.20150218.1.txt

Hello,

on 26/02/2105, r278964 seems to be part from the sa_changes patchset.
Do you have a sa_changes.stable_10.20150226 ready?
Or is it just a matter of exluding all parts, comitted with r278964 
from the patchset?
I've done so in the mean while:
ftp://ftp.omnilan.de/pub/FreeBSD/OmniLAN/misc/sa_changes.stable_10.20150226.fudge.patch

Noticed that in sys/dev/mps/mps_sas.c 'cdai.flags' gets conditionally
(#if __FreeBSD_version = 1100061) the new CDAI_FLAG_NONE, while in
sbin/camcontrol/camcontrol.c, this is unconditionally used. Haven't
really looked at the code, mostly because my skills wouldN#t allow me to
answer this qusteion myself, but is that versioncheck in mps_sas.c still
vaild with the rest of the sa_driver-changes?

Thanks,

-Harry



signature.asc
Description: OpenPGP digital signature


Re: [Call for testers] DRM device-independent code update to Linux 3.8 (take #2)

2015-03-07 Thread Alexander Kabaev
On Tue, 03 Mar 2015 23:33:23 +0100
Jean-S'ebastien P'edron dumbb...@freebsd.org wrote:

 Hi!
 
 Here is a new patch to based on HEAD r279508:
 https://people.freebsd.org/~dumbbell/graphics/drm-update-38.i.patch
 
 You can apply it to a Subversion checkout using the following command:
 svn patch drm-update-38.i.patch
 
 There are few changes:
 o  The panic reported by J.R. Oldroyd is fixed, but not the CP
 init problem.
 o  A lock assert was added, suggested by Konstantin Belousov
 
 I had several panics (Stray timeout) with a taskqueue used by TTM,
 but it didn't occur in the past 6 days. Maybe it was a problem
 outside of DRM.
 
 I would like people to test again and report :) If something fails,
 please post a full dmesg, taken after loading the relevant *kms
 module, or the core.txt.$N file if it's a panic.
 
 Hans Petter and Ed, I couldn't reproduce neither of your problems
 (HDMI hotplug events storm and VT-switch misbehaviour). However, they
 both involve callouts, like the Stray timeout panic I had with TTM.
 I suspect there was a transient problem with callouts in HEAD at the
 same time. Could you please test again with this patch and a very
 recent HEAD?
 
 Thank you to everyone!
 
 -- 
 Jean-S'ebastien P'edron
 

Just as a data point, 'stray timeout' happens in clean -current without
new patch as well. So whatever that is, it is not caused by the patch.

-- 
Alexander Kabaev


pgpg0MgLxRxxG.pgp
Description: OpenPGP digital signature


Re: upgrading current - graphics bug

2015-03-07 Thread David S

Which SVN revision do you use? `uname -a` should tell it.


r279687   compiled on Fri Mar  6 16:47:15 CET 2015

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: upgrading current - graphics bug

2015-03-07 Thread David S

FWIW the nVidia driver docs indicate that you should
comment, or remove the reference to dri in xorg.conf
#   Load  dri
but that dri2 is fine. Don't know that that has anything to
do with your issue. But thought I'd mention it FWIW.


thanks, i missed that part. i took it out of xorg.conf and will see 
next time i upgrade if it helps.

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: [Call for testers] DRM device-independent code update to Linux 3.8 (take #2)

2015-03-07 Thread Sam Fourman Jr.
 Just as a data point, 'stray timeout' happens in clean -current without
 new patch as well. So whatever that is, it is not caused by the patch.

 --
 Alexander Kabaev



I can confirm this, however, when it happens is RARE... it seems like it
happens when I am typing in the address bar of chromium.. im using HEAD
with a RAEDON on amd64

-- 

Sam Fourman Jr.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Call for FreeBSD 2015Q1 (January-March) Status Reports

2015-03-07 Thread Benjamin Kaduk
Dear FreeBSD Community,

The deadline for the next FreeBSD Quarterly Status update is April 7,
2015, for work done in January through March.

Status report submissions do not have to be very long.  They may be
about anything happening in the FreeBSD project and community, and
provide a great way to inform FreeBSD users and developers about what
you're working on.  Submission of reports is not restricted to
committers.  Anyone doing anything interesting and FreeBSD-related
can -- and should -- write one!

The preferred and easiest submission method is to use the XML
generator [1] with the results emailed to the status report team at
monthly at freebsd.org .  There is also an XML template [2] which can be
filled out manually and attached if preferred.  For the expected
content and style, please study our guidelines on how to write a good
status report [3].  You can also review previous issues [4][5] for
ideas on the style and format.

We are looking forward to all of your 2015Q1 reports!

Thanks,
Ben (on behalf of monthly@)


[1] http://www.freebsd.org/cgi/monthly.cgi
[2] http://www.freebsd.org/news/status/report-sample.xml
[3] http://www.freebsd.org/news/status/howto.html
[4] http://www.freebsd.org/news/status/report-2014-07-2014-09.html
[5] http://www.freebsd.org/news/status/report-2014-10-2014-12.html

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org


Re: r279514: buildworld failure: /usr/src/lib/libnv/tests/dnv_tests.cc:453:2: error: use of overloaded operator '' is ambiguous

2015-03-07 Thread Dimitry Andric
On 04 Mar 2015, at 22:31, Dimitry Andric d...@freebsd.org wrote:
...
 Hmm, I've now seen that there many more ATF_REQUIRE_EQ() instance in the
 tests, which compare against NULL.  It is rather cumbersome to fix all
 those, so maybe it should be fixed in atf-c++ instead.

It turns out there aren't so many after all.  See this review:

https://reviews.freebsd.org/D2027

-Dimitry



signature.asc
Description: Message signed with OpenPGP using GPGMail


Re: Pluggable frame buffer devices

2015-03-07 Thread Hans Petter Selasky

Hi Shawn,

I've just put some more pieces into the kernel.

https://svnweb.freebsd.org/changeset/base/279752
https://svnweb.freebsd.org/changeset/base/279753

Can you give the current code a spin?

To get X.org/X11 working simply create a config file under 
/usr/local/etc/X11/xorg.conf.d which contains the device section given 
by man xf86-video-scfb.


Open issues:

- Restoring the frame buffer does not always work. I looks like the 
restored text console size is 1x1 afterwards. At least there is no 
panic. And you can re-plug the UDL device again.


- You need to unplug the UDL device before rebooting.

- UDL device must be connected to a monitor before you plug it to USB, 
or you can load/unload the driver to re-probe the video format.


--HPS
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org