[This is in essence a notice of bug 209924 --found after working around 209920
in the cxgb and cxgbe areas.]
> --- all_subdir_drm2 ---
> In file included from
> /usr/src/sys/modules/drm2/i915kms/../../../dev/drm2/i915/dvo.h:35:0,
> from
>
Am 11. Juni 2016 18:31:25 MESZ, schrieb Alan Somers :
> On Sat, Jun 11, 2016 at 5:32 AM, Domagoj Stolfa
> wrote:
> > Yes, it would maybe make sense to do so. I am not too familiar with
> > capsicum(4), but glancing over it, it might be possible. If
> On Jun 12, 2016, at 18:28, Michael Gmelin wrote:
>
>
>
> On Sun, 12 Jun 2016 18:11:03 -0400
> Ngie Cooper wrote:
>
>>> On Jun 12, 2016, at 14:42, Joe Ennis wrote:
>>>
>>> On a vinalla, first pkg added, zfs on root install:
>>>
On Mon, Jun 13, 2016 at 9:44 AM, Florian Ermisch <
florian.ermi...@alumni.tu-berlin.de> wrote:
>
>
> Am 11. Juni 2016 18:31:25 MESZ, schrieb Alan Somers :
> > On Sat, Jun 11, 2016 at 5:32 AM, Domagoj Stolfa
> > wrote:
> > > Yes, it would maybe make
On 6/12/2016 7:14 PM, Simon J. Gerraty wrote:
> Mark Millard wrote:
>> Cross builds work just fine based on the FreeBSD tree when omitting
>> WITH_META_MODE=.
>>
>
> Hmm must do something odd then.
>
>> As of -r301825 there is almost no use of HOST_CC at the upper levels
With the newly less strict alignment requirements "kyua test -k
/usr/tests/Kyuafile" runs to completion, unlike before.
> ===> Summary
> Results read from
> /root/.kyua/store/results.usr_tests.20160613-080302-120731.db
> Test cases: 5694 total, 54 skipped, 21 expecte
Hi Imre
This is great information. Thank you!
My device have an emmc chip on the pcb (non-removable).
Have you tested you code on that kind of system?
Current unmodified FreeBSD can detect the sdhci_pci controller and a mmc
card on slot0 but timeouts when trying to init the mmc. Not sure why it
net> wrote:
> With the newly less strict alignment requirements "kyua test -k
> /usr/tests/Kyuafile" runs to completion, unlike before.
>
>> ===> Summary
>> Results read from
>> /root/.kyua/store/results.usr_tests.20160613-080302-120731.db
>> Test cas
strict alignment requirements "kyua test -k
>>> /usr/tests/Kyuafile" runs to completion, unlike before.
>>>
>>>> ===> Summary
>>>> Results read from
>>>> /root/.kyua/store/results.usr_tests.20160613-080302-120731.db
>>>
On 10/06/16 16:29, Peter Wemm wrote:
On 6/9/16 6:49 PM, Matthew Seaman wrote:
On 09/06/2016 18:34, Craig Rodrigues wrote:
There is still value to ypldap as it is now, and getting feedback from
users (especially Active Directory) would be very useful.
If someone could document a configuration
Hi,
I'm running into a somewhat weird issue with the rtwn driver
on CURRENT. It usually works for a couple of minutes (if there's
not too much of troughput happening) before the downstream and
upstream rates just "dry up" and the interface stops working.
It happens faster, if there are multiple
On 13 Jun 2016, at 12:09, Joel Dahl wrote:
>
>> On Mon, Jun 13, 2016 at 07:00:46AM -0400, Ngie Cooper (yaneurabeya) wrote:
>>
>>> On Jun 13, 2016, at 06:57, Joel Dahl wrote:
>>>
>>> Hi,
>>>
>>> I've just rebuilt and installed latest current on a machine here. I
I've been using the following script to run my make commands for amd64 builds
(as an example):
> # more
> ~/sys_build_scripts.amd64-host/make_amd64_nodebug_clang_bootstrap-amd64-host.sh
>
> kldload -n filemon && \
> script
>
On 6/13/2016 2:12 PM, Mark Millard wrote:
> I've been using the following script to run my make commands for amd64 builds
> (as an example):
>
>> # more
>> ~/sys_build_scripts.amd64-host/make_amd64_nodebug_clang_bootstrap-amd64-host.sh
>>
>> kldload -n filemon && \
>> script
>>
On 6/13/2016 2:51 PM, Ngie Cooper wrote:
> On Mon, Jun 13, 2016 at 2:12 PM, Mark Millard wrote:
>> I've been using the following script to run my make commands for amd64
>> builds (as an example):
>>
>>> # more
>>>
On 6/13/2016 2:54 PM, Ngie Cooper wrote:
> On Mon, Jun 13, 2016 at 2:52 PM, Bryan Drewery wrote:
> ...
>> The problem is that the y/n prompt don't show at all.
>
> Ah, I missed that critical point...
>
> Maybe MK_META_MODE=no should be forced for those targets?
I'm
On 2016-Jun-13, at 2:51 PM, Ngie Cooper wrote:
> On Mon, Jun 13, 2016 at 2:12 PM, Mark Millard wrote:
>> I've been using the following script to run my make commands for amd64
>> builds (as an example):
>>
>>> # more
>>>
On 2016-Jun-13, at 3:27 PM, Bryan Drewery wrote:
> On 6/11/2016 7:28 PM, Mark Millard wrote:
>> mergemaster [as an example] has code like:
>>
>>> # grep -i make /usr/sbin/mergemaster | more
>> . . .
>>> MM_MAKE="make ${ARCHSTRING} -m ${SOURCEDIR}/share/mk"
>>>
On 6/11/2016 9:55 PM, Mark Millard wrote:
> Doing cleanworld instead of "-j 5 buildworld buildkernel" and then retrying
> "-j 5 buildworld buildkernel" resulted in the same sort of thing but for
> maketab instead:
The cleanworld likely fixed an issue of a stale file sitting in the
objdir. I
On Mon, Jun 13, 2016 at 2:12 PM, Mark Millard wrote:
> I've been using the following script to run my make commands for amd64 builds
> (as an example):
>
>> # more
>> ~/sys_build_scripts.amd64-host/make_amd64_nodebug_clang_bootstrap-amd64-host.sh
>> kldload -n filemon && \
On Mon, Jun 13, 2016 at 2:52 PM, Bryan Drewery wrote:
...
> The problem is that the y/n prompt don't show at all.
Ah, I missed that critical point...
Maybe MK_META_MODE=no should be forced for those targets?
Thanks,
-Ngie
___
On 6/11/2016 7:28 PM, Mark Millard wrote:
> mergemaster [as an example] has code like:
>
>> # grep -i make /usr/sbin/mergemaster | more
> . . .
>> MM_MAKE="make ${ARCHSTRING} -m ${SOURCEDIR}/share/mk"
>> ${MM_MAKE} DESTDIR=${DESTDIR} distrib-dirs >/dev/null
>> ${MM_MAKE}
Bryan Drewery wrote:
> > eg. in our internal tree - which cross builds fine:
> >
> > make_keys: make_keys.c names.c ncurses_def.h ${HEADERS}
> > ${HOST_CC} -o $@ ${HOST_CFLAGS}
> > ${NCURSES_DIR}/ncurses/tinfo/make_keys.c
>
> I like this method but am going to put
t;> Results read from
>> /root/.kyua/store/results.usr_tests.20160613-080302-120731.db
>> Test cases: 5694 total, 54 skipped, 21 expected failures, 24 broken, 59
>> failed
>> Total time: 8723.243s
>
>
> I only list the one line summaries below. Then I list various
o run this code in a VM, or where I can get access to the
>>> hardware.
>>>
>>> -Alan
>>>
>>> On Mon, Jun 13, 2016 at 11:29 AM, Mark Millard <mar...@dsl-only.net> wrote:
>>>> With the newly less strict alignment requirements "kyua t
fore.
>>
>>> ===> Summary
>>> Results read from
>>> /root/.kyua/store/results.usr_tests.20160613-080302-120731.db
>>> Test cases: 5694 total, 54 skipped, 21 expected failures, 24 broken, 59
>>> failed
>>> Total time: 8723.243s
>>
>>
>>> ===> Summary
>>> Results read from
>>> /root/.kyua/store/results.usr_tests.20160613-080302-120731.db
>>> Test cases: 5694 total, 54 skipped, 21 expected failures, 24 broken, 59
>>> failed
>>> Total time: 8723.243s
>>
>
On 6/12/2016 5:39 AM, Simon J. Gerraty wrote:
> eg. in our internal tree - which cross builds fine:
>
> make_keys: make_keys.c names.c ncurses_def.h ${HEADERS}
> ${HOST_CC} -o $@ ${HOST_CFLAGS}
> ${NCURSES_DIR}/ncurses/tinfo/make_keys.c
I like this method but am going to put it off for
On 6/13/2016 7:26 PM, Mark Millard wrote:
> [The following is after the svnltie update -r301873 /usr/src .]
>
> For the following in a amd64 rebuild on amd64 (a WITH_META_MODE=yes
> buidlworld buidlkernel just after a without meta mode buildworld buildkernel
> [no install]). . .
>
>> # more
On 6/13/16 7:56 PM, Bryan Drewery wrote:
> On 6/13/2016 7:26 PM, Mark Millard wrote:
>> [The following is after the svnltie update -r301873 /usr/src .]
>>
>> For the following in a amd64 rebuild on amd64 (a WITH_META_MODE=yes
>> buidlworld buidlkernel just after a without meta mode buildworld
Bryan Drewery wrote:
> >> ${_FIRM}: ${.CURDIR}/../../../../contrib/dev/drm2/radeonkmsfw/${_FIRM}.uu
> >> uudecode -p $? > ${.TARGET}
Targets like this that use $? or ${.OODATE} are a bad fit with META mode.
If the normal make rules think the target is up to date,
On 6/13/16 8:18 PM, Simon J. Gerraty wrote:
> Bryan Drewery wrote:
${_FIRM}: ${.CURDIR}/../../../../contrib/dev/drm2/radeonkmsfw/${_FIRM}.uu
uudecode -p $? > ${.TARGET}
>
> Targets like this that use $? or ${.OODATE} are a bad fit with META mode.
>
> If
On Mon, Jun 13, 2016 at 07:00:46AM -0400, Ngie Cooper (yaneurabeya) wrote:
>
> > On Jun 13, 2016, at 06:57, Joel Dahl wrote:
> >
> > Hi,
> >
> > I've just rebuilt and installed latest current on a machine here. I noticed
> > the following message in dmesg after a reboot:
> >
>
> On Jun 13, 2016, at 06:57, Joel Dahl wrote:
>
> Hi,
>
> I've just rebuilt and installed latest current on a machine here. I noticed
> the following message in dmesg after a reboot:
>
> _secure_path: cannot stat /etc/login.conf: Not permitted in capability mode
>
> I don't
Hi,
Microsoft has some documentation on GPIO handling with SD card controllers,
which should apply to most Cherryview devices:
https://msdn.microsoft.com/windows/hardware/drivers/bringup/other-acpi-namespace-objects#sd
I did some work on Cherryview SoC support in DragonFlyBSD.
In DragonFly
Hi,
I've just rebuilt and installed latest current on a machine here. I noticed
the following message in dmesg after a reboot:
_secure_path: cannot stat /etc/login.conf: Not permitted in capability mode
I don't remember seeing this before.
--
Joel
Hi Imre
I got the device in /dev/mmcsd0. I think the reason was that mmcsd wasn't
loaded (need to load manually it seems..)
Do you think your patch in mmc is something that should be pushed upstream
in FreeBSD or is it more of a hack?
I am talking about
[The following is after the svnltie update -r301873 /usr/src .]
For the following in a amd64 rebuild on amd64 (a WITH_META_MODE=yes buidlworld
buidlkernel just after a without meta mode buildworld buildkernel [no
install]). . .
> # more sys/modules/drm2/radeonkmsfw/Makefile.inc
> # $FreeBSD:
or where I can get access to the
> > hardware.
> >
> > -Alan
> >
> > On Mon, Jun 13, 2016 at 11:29 AM, Mark Millard <mar...@dsl-only.net
> > > wrote:
> > > With the newly less strict alignment requirements "kyua test -k
> > > /usr/tests/
39 matches
Mail list logo