Hi all,
I'm working on getting the iwlwifi driver for intel devices into
the new wifi framework. In going over the files as named I see
that there are multiple different files "xxx/tx.c" and "yyy/tx.c".
Those names would both compile to tx.o in a kernel compile directory.
I haven't seen any ins
Hello,
I'm working with a student to get NetBSD working on the SiFive
HiFive Unleashed board. I know this is no longer being made, but
we have one. He has the kernel running on the board until it wants
to mount root. We want to get a sd driver working. The issue
is that the sd device is on
Hello,
I was wondering if anyone is working on solving PR 52347? "ww mutex class
mismatch"
I'm getting it averaging about once every other working day on my main machine.
8.99.34 did crash, but I couldn't get a good backtrace. This is a backtrace
for a
8.99.30 a few days ago.
# cras
On Thursday 26 July 2018 23:23:13 Taylor R Campbell wrote:
> static void
> foo_intr(...)
> {
> ...
> mutex_enter(&sc->sc_work_lock);
> if (!sc->sc_work_scheduled) {
> workqueue_enqueue(sc->sc_wq, &sc->sc_work, NULL);
> sc->sc_work_scheduled =
On Friday 27 July 2018 11:39:16 Mindaugas Rasiukevicius wrote:
> This is an indication that you are trying to acquire an adaptive lock
> while holding a spin-lock. Adaptive mutex (using IPL_NONE) blocks and,
> by design, you cannot block while holding a spin-mutex (> IPL_NONE).
> If you will inspe
On Thursday 26 July 2018 23:23:13 Taylor R Campbell wrote:
> Is this a conceptual problem, or do you have a symptom that you're
> actually hitting with specific code? If the latter, can you describe
> the symptom and quote the code?
Yes, this a real problem I'm having.
This is my real "f()":
s
Hello all,
I'm trying to work with workqueues and am having a locking problem
Lets say I have a function f() as follows:
int f() {
mutex_enter(&some_mutex);
.. code .
mutex_exit(&some_mutex);
}
and now lets say that I start another function runn
Hello,
Does anyone know if KGDB will work across a pcie serial card or does
it need to be the old motherboard ones?How about usb?
--Phil
On Thursday 12 July 2018 00:54:45 Martin Husemann wrote:
> You commented out a bit too much and it does not find your boot device?
>
> /*
> * If wildcarded root and we the boot device wasn't determined,
> * ask the user.
> */
> if (rootspec == NULL && boo
On Wednesday 11 July 2018 22:32:13 Patrick Welche wrote:
> "boot netbsd -a" ?
No, just "boot netbsd.wifi" to boot my special wifi kernel that I'm sure
will crash and don't want it doing an autoboot to.
--Phil
Hello,
Has anyone run into this? I created a special kernel for my 802.11 work
that removes a lot of unneeded drivers from my setup, stuff like raid, ntfs
and so forth. I got a working kernel out of it. Then, to work on the 802.11,
I commented out every 802.11 driver except the urtwn driv
Hello,
The FreeBSD 802.11 code is using a call to mtx_sleep(). The define is:
#define mtx_sleep(chan, mtx, pri, wmesg, timo) \
_sleep((chan), &(mtx)->lock_object, (pri), (wmesg), \
tick_sbt * (timo), 0, C_HARDCLOCK)
Just in case I ca
On Friday 06 July 2018 15:59:12 Jason Thorpe wrote:
> Anyway... in what situations is this absurd error code used in the 802.11
> code? EFAULT seems wrong because it means something very specific.
The code is in ieee80211_output.c and says:
/* locate destination node */
switch
On Friday 06 July 2018 12:09:55 Greg Troxel wrote:
> I might just map it to EFAULT or EINVAL.
I like this suggestion. EFAULT
--Phil
Hello,
In working on the 802.11 refresh, I ran into a new errno code from FreeBSD:
#define EDOOFUS 88 /* Programming error */
Shall we add this one? (Most likely with a different number since 88 is
taken
in the NetBSD errno.h.)
I could use EPROTO instead, but .
On Wednesday 25 April 2018 12:40:32 Tom Spindler (moof) wrote:
> > I'm a little late in trying 8.0 ... but I just tried to install 8.0 RC1 on a
> > Dell Optiplex 745. During boot it blanks the display and nothing can
> > be seen on the display from that point on.
>
> IIRC, I had similar issues
I'm a little late in trying 8.0 ... but I just tried to install 8.0 RC1 on a
Dell Optiplex 745. During boot it blanks the display and nothing can
be seen on the display from that point on.
The vga/display parts of the dmesg from 6.1.5 says:
vga1 at pci0 dev 2 function 0: vendor 0x8086 product
e safe, shouldn't it?
--Phil
--
Phil Nelson, http://pcnelson.net
her people have
successfully created file systems on 4k sector devices.
So, what am I doing wrong?
--Phil
--
Phil Nelson, http://pcnelson.net
life: http://goallpower.com
19 matches
Mail list logo