Hi!
So, my Lenovo T540p also doesn't work right now; it just panics the
kernel with a NULL pointer deref inside some deferred interrupt
registration / callback thing.
If I disable it at the boot console then it's fine.
-adrian
___
freebsd-current
lemme go see (again). That's why I wanted to re-review it all before I
landed stuff!
-a
On Fri, 2 Apr 2021 at 13:41, Bjoern A. Zeeb
wrote:
>
> On 2 Apr 2021, at 6:44, Adrian Chadd wrote:
>
> > I've got this in my local tree now.
>
> That’s not a good idea?
>
> &
I've got this in my local tree now. I have a note to go dig up which
draft I yanked this from and update it with reference to the draft and
the current spec.
Thanks for pointing this out!
-adrian
___
freebsd-current@freebsd.org mailing list
https
Hi!
Oh, so from what I recall, implementations got it wrong in the early
draft days with their interop so the flag values changed.
-adrian
On Thu, 1 Apr 2021 at 20:45, qcwap <1051244...@qq.com> wrote:
>
> Well, I see.
>
> I am newly to freebsd, thanks for your answering.
&
tcaps, IEEE80211_VHTCAP_SUPP_CHAN_WIDTH_MASK)
> >= \
This is the flag change from the draft 11ac spec to the released 11ac
spec, right?
I remember they needed to change the flags because existing draft
implementations got the 80+80/160MHz negotiation really badly wrong in
some interop place
I'm just testing the build out before I put up some patches.
jhb mentioned we don't install the libatomic gcc bits right now? So we
should likely poke at that somewhat too after this.
I'll put up some patches to fix gcc builds and this c++ contention thing
soon.
-adrian
On Sun, 4 Oct 2020
ping!
I've got the world building on gcc + mips32 just patching cxx_contention_t
to be 32 bits, but it looks like an ABI change.
Would the better thing be to just make it 32 bits on FreeBSD + MIPS for
now? I don't think anyone is going to mind that changing at this point.
-adrian
On Sat, 3
On Mon, 21 Sep 2020 at 00:43, Alexander Richardson
wrote:
>
> On Mon, 21 Sep 2020, 07:38 Adrian Chadd, wrote:
>
>> So, the big list of unknown symbols was my fault! Whoops.
>>
>> i've gotten further using gcc-6.4 by fixing some of the warnings/issues
>> that hav
/home/adrian/work/freebsd/head-embedded/obj/mips_ap/usr/home/adrian/work/freebsd/head-embedded/src/mips.mips/tmp/usr/lib/libc++.so.1:
undefined reference to `__atomic_fetch_sub_8'
/usr/local/bin/mips-unknown-freebsd13.0-ld:
/usr/home/adrian/work/freebsd/head-embedded/obj/mips_ap/usr/home/adrian/work
ux email lists as part discussion and
part RPC between everyones' git repositories.
I think this stuff predates github, where there's a much nicer web flow for
doing stuff like this.
The linux model works great in a world where you're /truely/ decentralised.
I bet that 99% of git users use some web fr
/home/adrian/work/freebsd/head-embedded/obj/mips_ap/usr/home/adrian/work/freebsd/head-embedded/src/mips.mips/tmp
-B/usr/local/mips-unknown-freebsd13.0/bin/ -O -pipe -fno-common
-DATJOB_DIR=\"/var/at/jobs/\" -DLFILE=\"/var/at/jobs/.lockfile\"
-DLOADAVG_MX=1.5 -DATSPOOL
hi!
This code fails compilation on mips32 + gcc, as it assumes uint64_t and
pointer casts are the same underlying size.
===
/usr/local/bin/mips-unknown-freebsd13.0-gcc9
--sysroot=/usr/home/adrian/work/freebsd/head-embedded/obj/mips_ap/usr/home/adrian/work/freebsd/head-embedded/src/mips.mips/tmp
On Sun, 13 Sep 2020 at 22:34, Warner Losh wrote:
>
>
> On Sun, Sep 13, 2020, 11:29 PM Adrian Chadd
> wrote:
>
>> Yeah, this was also reported in #freebsd-wireless today.
>>
>> Is there a lock being held in the rtwn path that shouldn't be?
>>
>
&g
Yeah, this was also reported in #freebsd-wireless today.
Is there a lock being held in the rtwn path that shouldn't be?
-adrian
On Sun, 13 Sep 2020 at 21:30, Warner Losh wrote:
> I'm running current as of -2h ago.
>
> When I plug in my rtwn0 device and it configures, etc, I get:
> What might be curious about it is that there are usb, i2c and gpio mixed
> together.
>
Any interest at all?
> I am still torn about which of the approaches to take.
>
I prefer the non monolithic one. i left comments on that one. :-)
-adrian
> --
> Andriy Gapon
> ___
cbgroup inpcb list and that isn't doable if you're waiting for
hardware flowid first.
Honestly I think we should rename it to something else besides RSS,
cause it's more like PCBGROUPS + microsoft RSS. It's not very well
named right now and I think it's confusing tf
Ie igb hardware here. I /think/ I do but it's fibre.
-adrian
___
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"
y
> > in freebsd-wifi-build project, so this should not be a problem in the
> > future.
> >
> > But isn't it has to be fixed right now until we get a replacement?
> >
>
> I'd be inclined to agree. Unless Adrian objects, I think it'd be a
> good idea to go ah
I've no idea, bgscan is broken with atheros NICs because the driver still
doesn't do background scan without dropping frames :(
(one of many thing I'd love to fix, but life/time.)
please do experiment though! I think wpa_supplicant's roaming logic would
benefit from a lot more work.
-adrian
bgscan too periodically rather than only when the RSSI is low.
-adrian
On Thu, 19 Sep 2019 at 15:04, Cy Schubert wrote:
> On September 19, 2019 8:20:07 AM PDT, Adrian Chadd
> wrote:
> >Roaming is done in wpa_supplicant when it's running.That's where the
>
Roaming is done in wpa_supplicant when it's running.That's where the smarts
need to be. :(
-adrian
On Thu, 19 Sep 2019 at 05:44, Bjoern A. Zeeb
wrote:
> On 19 Sep 2019, at 12:28, Tom Jones wrote:
>
> Hi,
>
> freebsd-wireless might be a better list for all this ..
>
&g
hi,
I'm trying to update things with Geramy right now. We hit a snag where his
updates broke my QCA9880 NIC in STA mode, so we're working through that
right now.
-adrian
On Mon, 11 Feb 2019 at 09:51, Ben Widawsky wrote:
> On 19-02-04 00:29:29, Anthony Jenkins wrote:
>
> [sni
rather than the array of static
tables..
-adrian
On Thu, 22 Nov 2018 at 09:05, Steve Kargl
wrote:
> I have an old D-Link AirPlus G (DWL-630) pccard card
> that I have used for years with FreeBSD. Recently,
> I see
>
> % dmesg | grep ath
> mobile:kargl[201] dmesg | grep ath
And I think 0x1b is "1mbit CCK", so I bet that's disabled on your AP?
On Fri, 23 Nov 2018 at 11:28, Adrian Chadd wrote:
> hi!
>
> No. It's a side effect of how ath_rate_sample works. The TL;DR is:
>
> * ath_rate_sample uses a fixed set of rates for each attempt - so s
Hi,
Aren't there now per-domain VM counters you can query via sysctl?
Maybe they'd help in diagnosing what's going on.
-adrian
On Mon, 25 Jun 2018 at 11:23, Steve Kargl
wrote:
>
> On Sun, Jun 24, 2018 at 12:03:29PM +0200, Alexander Leidinger wrote:
> >
> > I don't
hm. Which country are you in? india?
It seems to think you're in the FCC4 regdomain and DE country, which
if I read it right won't give you 5G. So somehow it determined you're
in the "wrong" country?
-adrian
On Mon, 4 Jun 2018 at 07:15, Adam wrote:
>
> On Sun, Jun 3,
Dude, we're on the same side. I'll take a look at the multicast
iterator stuff once I figure out why the athp receive performance in
my driver is terrible-y.
-adrian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/list
Hi,
If there's an API that isn't being used then great, I'll go find it
and fix up pieces in my spare time to use it. But the last drive by
cut/paste didn't do that; it just changed the code in place. :-)
-adrian
___
freebsd-current@freebsd.org
r intel NIC - I'm sorry that you've had issues getting that
into the tree but you can just jump in #freebsd-wifi and whine at us
until we commit it. That's what we're there for.
-adrian
___
freebsd-current@freebsd.org mailing list
https://lists.freeb
timers? Maybe a dtrace
probe on the callout schedule entry point?
-adrian
___
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"
e MD.
>
> On x86, the CPUID instruction leaf 0x1 returns the information in
> %ebx register.
Hm, weird. Why don't we extend sysctl to include this info?
-adrian
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mail
Hi,
Have a look at what the atheros ports now do. They've been building
using the external toolchain gcc for a while now.
I think we need to kick over to that.
-adrian
On 11 November 2017 at 12:54, Michael Zhilin <miz...@gmail.com> wrote:
> Hi,
>
> I've got compilation e
is available then please do so. Or, just
support the firmware being 100% compiled in- but when I tried this the
last time I ran out of some firmware arena size preventing other
firmware for other chipsets from being loaded.
Otherwise this is the current hack. :)
Sorry!
-adrian
[snip]
yes you need to rebuild; the ioctl layout changed between -11 and -12
to account for the beginnings of 11ac.
-adrian
On 17 October 2017 at 11:30, Cy Schubert <cy.schub...@komquats.com> wrote:
> I had no problems last night. It associated with one of my netgear APs. I
&g
ys but I'm
busy with family and employment.
-adrian
On 16 October 2017 at 10:19, Kevin Oberman <rkober...@gmail.com> wrote:
> On Mon, Oct 16, 2017 at 8:55 AM, Adrian Chadd <adrian.ch...@gmail.com>
> wrote:
>>
>> hi,
>>
>> I got the patches a couple days
everything to but so far nope. It should be easy enough to update the
port for now as it's at 2.6.
-adrian
On 16 October 2017 at 06:04, Cy Schubert <cy.schub...@komquats.com> wrote:
> In message <44161b4d-f834-a01d-6ddb-475f20876...@freebsd.org>, Lev Serebryakov
> writes:
>
I'm sure stas can figure it out!
-a
On 25 June 2017 at 22:44, Thomas Mueller <mueller6...@twc.com> wrote:
> from Adrian Chadd:
>
>> valgrind broke as part of the ino64 work :(
>
> Valgrind was not on my mind! Your post sent me to
>
> ls -d /usr/ports/*/val*
>
Hi,
valgrind broke as part of the ino64 work :(
-a
___
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"
hi!
Thanks! Yes please let's update the handbook at least.
-a
On 23 June 2017 at 10:06, Renato Botelho <ga...@freebsd.org> wrote:
> On 23/06/17 13:43, Adrian Chadd wrote:
>> Hi,
>>
>> You can't change a wifi mac address /after the interface is up/. So if
>&
Hi,
You can't change a wifi mac address /after the interface is up/. So if
that's happening with this RC script combination then we should kinda
fix that.
-adrian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo
y the driver" module
> ath.ko or some such.
Oh yeah, I could also do that to reduce POLA. :)
Ok, I'll add that to the TODO list before I submit a review. I'll
rename if_ath to if_ath_drv or something.
-adrian
___
freebsd-current@freebsd.org mailing li
find your hardware.
I realise this is a bit of a POLA change, but I'd like to get it into
-HEAD before FreeBSD-12 is cut.
Thanks!
-adrian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
On 17 May 2017 at 23:37, Warner Losh <i...@bsdimp.com> wrote:
> On Wed, May 17, 2017 at 11:53 PM, Baptiste Daroussin <b...@freebsd.org> wrote:
>> On Wed, May 17, 2017 at 06:04:09PM -0700, Adrian Chadd wrote:
>>> https://reviews.freebsd.org/D10778
>>&
https://reviews.freebsd.org/D10778
-a
On 17 May 2017 at 17:46, Adrian Chadd <adr...@freebsd.org> wrote:
> hi,
>
> this is a quick change that makes concurrency_kit a module. Right now
> the only thing using it is linuxkpi so it's all dead code on
> non-linuxkpi platf
hi,
this is a quick change that makes concurrency_kit a module. Right now
the only thing using it is linuxkpi so it's all dead code on
non-linuxkpi platforms.
-adrian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman
There were lots of commits that could break things. :-)
Can you compile up some intermediary versions between 315141 and
r317559 to find which commit range broke things? That'll make chasing
it down much quicker!
Thanks!
-a
On 29 April 2017 at 04:50, Manuel Stühn
B_PCI0IGPUGSCI�K p
>>>
>>> Might be related to:
>>> https://bugs.freedesktop.org/show_bug.cgi?id=98501
>>>
>>>
>>>
>>> On Wed, Apr 5, 2017 at 8:15 PM, Ngie Cooper (yaneurabeya)
>>> <yaneurab...@gmail.com> wrote:
>>&
It'll be supported as much as someone is willing to pay for it.
It isn't out of the realm of possibility to implement an if_transmit
style layer for altq, etc so it could be a generic queue discipline.
It'd be nice to have a multi-queue version of this but we're not there
yet.
Thanks,
-adrian
hm, you could use dtrace to find what's calling that function and
print out the call stack?
-adrian
On 5 April 2017 at 02:32, Johannes Lundberg <johal...@gmail.com> wrote:
> Is there an easy way to do that with existing tools or do I need to add
> debug printing to the code?
>
hiya,
looks like yeah, you're going to have to do a bit more debugging. Can you
see what args are being passed to AcpiNsLookup() ?
-adrian
On 3 April 2017 at 03:24, Johannes Lundberg <johal...@gmail.com> wrote:
> Hi Adrian
>
> The three threads are kernel(acpi_task_{0-2}) a
I don't /think/ so - which thread is it on your end? Can you run
pmcstat -S instructions -T to see what's taking your CPU?
-adrian
On 28 March 2017 at 13:36, Johannes Lundberg <johal...@gmail.com> wrote:
> Hi
>
> Personally I got some acpi-something kernel thread at 100% CPU c
hiya,
I've noticed that my battery life on my haswell laptop (T540p) seems
to have taken a nosedive lately. I could've /sworn/ it was getting
better than 15-16W at idle.
Has anyone noticed any massive decrease in battery life lately?
-adrian
WITHOUT_CLANG fixed it for me. Thanks.
-adrian
On 20 March 2017 at 11:23, Ed Maste <ema...@freebsd.org> wrote:
> On 19 March 2017 at 03:00, Adrian Chadd <adr...@freebsd.org> wrote:
>> gcc version 5.3.0 (FreeBSD Ports Collection for mips)
>>
>> ... so
===> lib/clang (all)
===> lib/clang/libllvm (all)
In file included from
/usr/home/adrian/work/freebsd/head-embedded/obj/mips_ap/mips.mips/usr/home/adrian/work/freebsd/head-embedded/src/tmp/usr/include/c++/v1/math.h:309:0,
from
/usr/home/adrian/work/freebsd/head-embedd
On 2 March 2017 at 01:31, Matthias Apitz <g...@unixarea.de> wrote:
> On Thursday, 2 March 2017 00:37:35 CET, Michael Gmelin <free...@grem.de>
> wrote:
>>
>>
>>
>>> On 2 Mar 2017, at 00:35, Adrian Chadd <adrian.ch...@gmail.com> wrote:
>>>
This is an emulated BIOS though, right?
I don't know if we're going to get the RTC 'bugfixed'...
-adrian
On 28 February 2017 at 15:26, Michael Gmelin <free...@grem.de> wrote:
> On Tue, 28 Feb 2017 17:16:02 -0600
> Eric van Gyzen <vangy...@freebsd.org> wrote:
>
>>
because:
>>
>> ...
>> ===> iwifw/iwi_ibss (all)
>> --- all_subdir_iwifw/iwi_monitor ---
>> ===> iwifw/iwi_monitor (all)
>> --- all_subdir_ipmi ---
>> --- all_subdir_ipmi/ipmi_linux ---
>> ===> ipmi/ipmi_linux (all)
>&g
ok, lemme do a build and if it succeeds i'll commit it
-a
On 16 February 2017 at 06:39, Johannes Lundberg <johal...@gmail.com> wrote:
> My emacs remove trailing white spaces automatically on save.
>
> On Wed, Feb 15, 2017 at 22:59 Adrian Chadd <adrian.ch...@gmail.com> wr
this looks fine to me. what's with the whitespace changes?
-a
On 15 February 2017 at 19:27, Johannes Lundberg wrote:
> Hi
>
> This patch adds support for MacBook Pro 11,2 to asmc.
>
> The other day I tried patching my old
>
>
want to do the right thing even if it takes longer. Really appreciate you
> taking the time to respond, thanks!
>
> Anindya
>
> From: Adrian Chadd [adrian.ch...@gmail.com]
> Sent: January 20, 2017 3:11 PM
> To: Anindya Mukherjee
>
t 'creator' and
'creator_vt' did in sys/dev/fb/ . It's just sad that the vt interface
to the screen buffer isn't as complete as the older school framebuffer
interface is.
-adrian
On 19 January 2017 at 12:35, Anindya Mukherjee <anindy...@hotmail.com> wrote:
> Hi Adrian,
>
> I was looking
to provide increasing functionality - but that's a lot to ask given
the complexity of the current system.
2c,
-adrian
On 15 January 2017 at 09:08, Tijl Coosemans <t...@freebsd.org> wrote:
> Hi,
>
> The latest version of x11/nvidia-driver contains a call to a syscons
> func
heh.
As always, patches gratefully accepted. :)
-adrian
On 14 January 2017 at 21:07, Ernie Luzar <luzar...@gmail.com> wrote:
>
> You can add these things to the vt to-do list
>
> Change the default font to look like sc.
> Add copy/paste function like sc has.
> Add sp
hi,
no, the vt_vga backend doesn't yet do VESA.
I keep meaning to sit down and fix this, but life and wifi gets in the way.
-adrian
On 14 January 2017 at 16:27, Kevin Oberman <rkober...@gmail.com> wrote:
> On Sat, Jan 14, 2017 at 2:11 PM, Adrian Chadd <adrian.ch...@gmail.
It depends(tm). I think the VT code just does "640x480x4bpp" and lets
the BIOS sort it out. A lot of things don't cope well with 640x480
these days - they try autodetecting picture edges, but a black border
makes that very difficult.
-adrian
On 14 January 2017 at 08:57, Matth
hi!
no, and maybe.
-a
On 9 January 2017 at 05:30, tech-lists wrote:
> Hello lists,
>
> [x-posted to freebsd-arm because this question appears to be equally
> relevant there]
>
> Does the onboard wireless on the raspberry pi 3 work in 12-current-aarch64?
>
> If not, are
email freebsd-wireless with the wifi details. i know our iwm driver
gets antenna configs wrong sometimes and that can cause issues.
-a
On 6 January 2017 at 11:07, Jonathan Anderson wrote:
> On 6 Jan 2017, at 13:53, Pete Wright wrote:
>>
>>
>> i've been having the same
*mumble* damnit jordan this requires libdispatch *mumble*
-a
___
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"
On 19 December 2016 at 16:04, Jordan Hubbard <j...@mail.turbofuzz.com> wrote:
>
> On Dec 19, 2016, at 12:27 PM, Adrian Chadd <adrian.ch...@gmail.com> wrote:
>
> So although I like the sentiment, I don't think using dtrace for
> program logging is the right answer. I
o people didn't just write their own
libraries (hi!) and so there's a unified-ish way to interact with
apple programs. I think we could do with that.
Thanks,
-adrian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/list
xposing it as thread local storage, or a VDSO syscall,
> would be nicer because the kernel knows when it is actually changing
> value.
The problem is your CPU ID can change in the middle of packet handling.
So if you want it to be accurate, you need to bind your worker thread to a CPU.
-adrian
___
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"
of is some hack to add a blacklist for that region so
you can boot the unit. But it makes me wonder what else is going on.
-adrian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, sen
some help with
that.
If you're interested in helping out and can take some direction then
sign up and we'll figure the bits out.
Thanks!
-adrian
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To u
On 26 November 2016 at 13:59, Slawa Olhovchenkov <s...@zxy.spb.ru> wrote:
> On Sat, Nov 26, 2016 at 01:55:14PM -0800, Adrian Chadd wrote:
>
>> ok, hm. then i don' know offhand, not without putting in printf debugging. :)
>
> I am not expert in this code, I am need you patc
ok, hm. then i don' know offhand, not without putting in printf debugging. :)
-a
On 26 November 2016 at 13:51, Slawa Olhovchenkov <s...@zxy.spb.ru> wrote:
> On Sat, Nov 26, 2016 at 01:49:00PM -0800, Adrian Chadd wrote:
>
>> Ok. So boot verbose and let's see what it says.
>
Ok. So boot verbose and let's see what it says.
-adrian
On 26 November 2016 at 10:39, Slawa Olhovchenkov <s...@zxy.spb.ru> wrote:
> On Sat, Nov 26, 2016 at 09:44:49AM -0800, Adrian Chadd wrote:
>
>> The ACPI SRAT parsing code - sys/x86/acpica/srat.c .
>>
>> I'd
The ACPI SRAT parsing code - sys/x86/acpica/srat.c .
I'd start by enabling bootverbose - adds one echo (SLIT.Localities and
the table); adds CPU affinity info (legacy, XAPIC, ACPI) and other
locality stuff.
-adrian
On 26 November 2016 at 09:37, Slawa Olhovchenkov <s...@zxy.spb.ru>
It may be something to do with memory topology parsing. Maybe we need
some more debugging there to try and catch it.
-a
On 26 November 2016 at 01:21, Slawa Olhovchenkov wrote:
> I am try to enable NUMA in bios and can't boot FreeBSD.
> Boot stoped after next messages:
>
>
Hiya,
Just to follow through - part of tput is to decode command args, but
it then just requests it from the ncurses tputs() call.
So it could be tput, but it could also be the BSD ncurses work.
-adrian
On 21 November 2016 at 07:54, Julian Elischer <jul...@freebsd.org> wrote:
>
+10 on option 2. Hate to say it, but I'd rather this little corner of
freebsd be "right" before it gets more heavily used.
-a
On 10 November 2016 at 03:21, Andriy Gapon wrote:
> On 14/10/2016 18:51, Lewis Donzis wrote:
>> Our opinion doesn’t count for much, but I like 2 or
I don't know why it's hanging; and unfortunately I'll have to
reinstall -head to get a working console (since the device I have here
for doing ppc+bwn work wants syscons, /not/ vt.. :( )
-a
On 6 November 2016 at 14:42, Justin Hibbits wrote:
> Hi folks,
>
> I have a
Hiya,
So uhm - normal rtwn works fine, but andriy's merged version doesn't?
-a
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
hi,
can you turn on debugging? Do you see RX frames?
-a
On 1 October 2016 at 08:09, Kevin Lo wrote:
> Strange, rtwn(4) stops working. I tried to scan for the available network,
> but it just returns empty results.
>
> On Fri, Sep 23, 2016 at 02:44:13PM +0300, Andriy
hi,
I'll try it out tonight! Is the rtwn repo still "ok" to try as a
standalone thing?
The usbdevs patch is fine standalone - would you like to just commit
this in advance?
-adrian
On 19 September 2016 at 06:26, Andriy Voskoboinyk <a...@freebsd.org> wrote:
> Thu, 01 Sep
hi,
bluetooth uses netgraph.
-a
On 15 September 2016 at 11:36, Steve Kargl
wrote:
> I recently got a spanky new Dell Precision 7510. After
> freeing up space on the nvme device, I installed
> FreeBSD-12.0-CURRENT-amd64-20160829-r305028-memstick.img
> on
is it too new to "kldload i915kms" ?
-adrian
On 9 September 2016 at 00:45, Philip Homburg <pch-fbs...@u-1.phicoh.com> wrote:
>>What graphics driver are you using?
>
> Just the default:
> 'VT(vga): resolution 640x480'
>
> Booting with -v and switching
Try forcing a console switch - hit alt-f1, alt-f2, etc.
-a
On 8 September 2016 at 15:10, Glen Barber wrote:
> On Thu, Sep 08, 2016 at 11:32:24PM +0200, Philip Homburg wrote:
>> The main culprit seems to be putting 'hw.acpi.reset_video=1' in
>> /boot/loader.conf
>>
>
> Yes, I
So sometimes
the scan results list in wpa_supplicant returns prematurely and it
doesn't know to fetch an updated one.
-adrian
On 6 September 2016 at 13:17, Andreas Nilsson <andrn...@gmail.com> wrote:
> Hello,
>
> I installed 12-CURRENT from a few days ago on my laptop ( thinkpad
Hey, this looks really cool!
-a
On 5 September 2016 at 06:25, bbjowhn . wrote:
> I'm guessing most of you seeing this post aren't too familiar with the
> project, so I'll start with something of a synopsis.
>
> Arcan is a mix between a streaming realtime graphics (and
hi,
no, ar988x is 11ac, and i haven't finished the port.
-a
On 3 September 2016 at 06:36, O. Hartmann wrote:
> Am Sat, 3 Sep 2016 15:25:17 +0200
> Guido Falsi schrieb:
>
>> On 09/03/16 15:11, O. Hartmann wrote:
>> > Am Sat, 3 Sep 2016 14:01:15
On 25 August 2016 at 12:45, Stefan Wendler wrote:
> Hi,
>
> is this fixed in RC2? I haven't tried it yet but would be nice to know
Hi,
Just so everyone who may be interested/involved can see - I don't have
the spare bandwidth/cycles to try and make wifi + lagg
hiya,
This seems to be needed for compiling elftoolchain under gcc-5.3
targeting mips (CROSS_TOOLCHAIN=mips-gcc) otherwise it complains that
sz isn't always initialised:
adrian@gertrude:~/work/freebsd/head-embedded/src % svn diff contrib
Index: contrib/elftoolchain/elfcopy/ascii.c
w!
ok, what has to be committed to -head?
-a
On 13 August 2016 at 19:12, Lundberg, Johannes
wrote:
> Hi FreeBSD hackers!
>
> Today we reached a big milestone. For the first time, we could render
> Wayland clients, backed by hardware, not shm (shared
CCA_CHUNK = (1 << 31)
>> > }; /* IWM_TX_FLAGS_BITS_API_S_VER_1 */
>> >
>> > -/**
>> > - * enum iwm_tx_pm_timeouts - pm timeout values in TX command
>> > - * @IWM_PM_FRAME_NONE: no need to suspend sleep mode
>> > - * @IWM_PM_FRAME_MGMT: fw s
Hi,
Did you test on any 1, 2, 4, 8 cpu machines? just to see if there are
any performance degredations on lower count CPUs?
Also, yeah, the MOD operator in each loop could get spendy on older
CPUs (eg my MIPS CPUs, older ARM stuff, etc.) Is it possible to
achieve much the same autotuning with
+imre,
Hi! Larry is having issues with r303418. Would you be able to help him out?
(If it's not too bad, can we back this out until you figure out what's
going on?)
Thanks!
-a
On 28 July 2016 at 18:05, Larry Rosenman <l...@lerctr.org> wrote:
> On 2016-07-28 20:02, Adrian Ch
Hi,
Which commit(s) did you revert?
-a
___
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"
Hi,
Andriy responded?
-adrian
On 28 July 2016 at 16:04, Larry Rosenman <l...@lerctr.org> wrote:
> Anyone?
>
>
> On 2016-07-27 21:39, Larry Rosenman wrote:
>>
>> I'm running today's top of tree, and it doesn't seem to want to connect:
>>
>>
>&
heh, nice catch. Would you please file a PR so we don't forget?
Thanks!
-a
On 19 July 2016 at 08:35, Hartmut Brandt wrote:
> Hi,
>
> I'm trying to use asio (that's boost::asio without boost) to handle
> listening sockets asynchronuosly. This appears not to work. There
Hi,
Just try disabling the others and see what happens.
Thanks!
-a
On 15 July 2016 at 13:28, Wolfgang Zenker <wolfg...@lyxys.ka.sub.org> wrote:
> * Adrian Chadd <adr...@freebsd.org> [160715 00:00]:
>> On 14 July 2016 at 14:37, Wolfgang Zenker <wolfg...@lyxys.ka.sub.
1 - 100 of 1325 matches
Mail list logo