User Details
- User Since
- May 14 2014, 7:57 AM (626 w, 5 d)
Today
This looks good; how would we unit test this behaviour?
Yesterday
Fri, May 15
add some receive documentation
Want to rebase this to use the net80211_rssi_t once that diff lands?
Wed, May 13
Tested on my intel comet lake desktop w/ nvme attached via an ahci sata/raid integrated, worked just fine.
Mon, May 11
Sun, May 10
ok, this looks better. ngie@, anything else?
finish my first pass at the transmit path overview
Sat, May 9
more stuff
Fri, May 8
Add some more transmit datapath overview documentation.
Thu, May 7
this LOOKS right to me. @ngie any other comments?
tagging christos@ as this is an audio thing.
Wed, May 6
Tue, May 5
what's the earliest chipset this supports? (eg the Atom C2xxx / C3xxx ones?)
I do have test C2558 w/ the different register offset for the power register AND C3xxx atom boxes (and a lot of non-atom stuff dating back to sandybridge at least) so i'm happy to test this on wahtever you'd like. but yes please do not ignore the "odd one out".
Mon, May 4
Sun, May 3
already landed in 0de6295af231aa5c13e1da2f40b29106962b6363
oh good question, lemme go do some digging. It's likely worth seeing what linux is doing and some of the older wifi stacks that are floating about.
Fri, May 1
add MVP debug API section
please fix the hyphen and then this'll be fine to land, thanks!
Thu, Apr 30
update
rebase
rebase
rebase
update
rebase
rebase
rebase after jhb's vm_offset_t changes
Thanks heaps for this!
this looks fine to me, anyone else?
Wed, Apr 29
Mon, Apr 27
Sun, Apr 26
Wed, Apr 22
what do i need to check in dmesg / pciconf to see if i have something that can test this?
as long as ivy's stuff is covered, yeah, land it.
