> Message: 1
> Date: Thu, 11 Sep 2014 15:23:07 +0200
> From: Nick Hibma
> To: freebsd-current@FreeBSD.ORG
> Cc: Hans Petter Selasky
> Subject: CDC-WDM driver (4G modems)
> Message-ID: <2d4cf978-b2c2-4253-93c7-595dabac0...@van-laarhoven.org>
> Content-Type: text/plain; charset=us-ascii
>
> F
> --
>
> Message: 4
> Date: Wed, 7 Mar 2012 10:45:11 -0800
> From: Adrian Chadd
> Subject: Re: patches for if_iwi and wlan for WEP mode
> To: Mitsuru IWASAKI
> Cc: freebsd-current@freebsd.org, freebsd-wirel...@freebsd.org,
> bschm...@freebsd.org
> Message-ID:
>
On Fri, Jul 8, 2011 at 1:35 AM, Hans Petter Selasky wrote:
> On Friday 08 July 2011 03:25:39 PseudoCylon wrote:
>> On Thu, Jul 7, 2011 at 6:47 AM, Hans Petter Selasky
> wrote:
>> > On Thursday 07 July 2011 14:43:22 PseudoCylon wrote:
>> >> On Wed, Jul 6, 201
On Thu, Jul 7, 2011 at 6:47 AM, Hans Petter Selasky wrote:
> On Thursday 07 July 2011 14:43:22 PseudoCylon wrote:
>> On Wed, Jul 6, 2011 at 9:19 AM, Hans Petter Selasky
> wrote:
>> >> Hi,
>> >>
>> >> I'm going to review and import your driver.
On Wed, Jul 6, 2011 at 9:19 AM, Hans Petter Selasky wrote:
>>
>> Hi,
>>
>> I'm going to review and import your driver.
>>
>> --HPS
>
> Hi,
>
> The intial patch had some bad code and didn't compile on 9-current. I've tried
> to clean it up. Please test and report back if I didn't break anything.
>
- Original Message -
> From: Hans Petter Selasky
> To: freebsd-current@freebsd.org; PseudoCylon
> Cc: "freebsd-wirel...@freebsd.org"
> Sent: Tuesday, June 28, 2011 12:50:57 AM
> Subject: Re: [CFT] Sierra Wireless HSPA+ USB modem
>
> On Tuesday 28 June
Hello
Here is a driver for Sierra Wireless HSPA+ USB modem. Please test it. My
subscription will expire on June 29, 2011. (Yes, it sounds silly.) So, try it
before too late.
source tree https://gitorious.org/usie/usie/trees/master
tarball https://gitorious.org/usie/usie/archive-tarball/master
> > rt28600: mem 0xf7f0-0xf7f0 irq 17 at
> > device 0.0 on pci3
> > rt28600: invalid EEPROM LNA gain #2: 0x00
> > rt28600: invalid EEPROM LNA gain #3: 0x00
> > rt28600: invalid EEPROM powersave level
> > rt28600: MAC/BBP RT2860 (rev 0x28720200), RF RT3022 2.4G 2T2R
> Wow, your device h
> >>
> >> I urge you to have a closer look at ral(4) and it's way of handling
> >> RT2500 and RT2600 specific differences. In it's simplest form you can
> >> copy the OpenBSD code 1:1 without any functional changes, heck, it's
> >> the source of this driver anyway.
> >>
> >> --
> >> Bernhard
> >
> > hostname.if(5) is something that only exists in OpenBSD.
> > I think the following would be better:
> > For more information on configuring this device, see
> > .Xr ifconfig 8 .
> >
>
> Hi,
>
> This is still relevant. hostname.if(5) is in OBSD.
> Will someone fix this?
>
> --
> wbr,
- Original Message
> From: Rui Paulo
> To: PseudoCylon
> Cc: Bernhard Schmidt ; freebsd-current@freebsd.org;
>Adrian Chadd
> Sent: Wed, September 22, 2010 4:48:14 PM
> Subject: Re: RFT: if_ath HAL refactoring
>
> On 22 Sep 2010, at
- Original Message
> From: Bernhard Schmidt
> To: freebsd-current@freebsd.org
> Cc: PseudoCylon ; Adrian Chadd
> Sent: Wed, September 22, 2010 12:09:36 AM
> Subject: Re: RFT: if_ath HAL refactoring
>
> On Wednesday, September 22, 2010 06:04:49 PseudoCylon wrote
- Original Message
> From: Adrian Chadd
> To: PseudoCylon
> Cc: freebsd-current@freebsd.org
> Sent: Tue, September 21, 2010 7:04:37 AM
> Subject: Re: RFT: if_ath HAL refactoring
>
> On 21 September 2010 11:58, PseudoCylon wrote:
>
> > Just in case
> Message: 9
> Date: Sun, 19 Sep 2010 01:04:47 +0800
> From: Adrian Chadd
> Subject: Re: RFT: if_ath HAL refactoring
> To: Brandon Weisz
> Cc: freebsd-current@freebsd.org
> Message-ID:
>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On 19 September 2010 01:01, Adrian Chadd wrote:
: Hans Petter Selasky
> To: freebsd-current@freebsd.org
> Cc: PseudoCylon ; Sam Leffler ;
>freebsd-...@freebsd.org
> Sent: Wed, July 21, 2010 10:00:26 AM
> Subject: Re: [panic] Race in IEEE802.11 layer towards device drivers
>
> Hi,
>
> Please confirm that
- Original Message
> From: Hans Petter Selasky
> To: PseudoCylon
> Cc: freebsd-current@freebsd.org; Sam Leffler ;
>freebsd-...@freebsd.org
> Sent: Tue, July 20, 2010 4:46:34 AM
> Subject: Re: [panic] Race in IEEE802.11 layer towards device drivers
>
> On Tuesd
- Original Message
> From: Hans Petter Selasky
> To: freebsd-current@freebsd.org
> Cc: PseudoCylon ; Sam Leffler ;
>freebsd-...@freebsd.org
> Sent: Mon, July 19, 2010 1:17:04 PM
> Subject: Re: [panic] Race in IEEE802.11 layer towards device drivers
>
> Hi AK,
[NB] Obviously, I didn't click "reply ALL" last time, so here are missing part
> > > > -if(vap->iv_opmode == IEEE80211_M_HOSTAP){
> > > >
> > > > -RUN_LOCK(sc);
> > > > +if (vap->iv_opmode == IEEE80211_M_HOSTAP)
> > > >
> > > > sc->cmdq_key_set = RUN_CMDQ_GO;
> > > >
> > > > -RUN_UNLOCK(sc)
- Original Message
> From: Ganbold
> To: PseudoCylon
> Cc: Ganbold Tsagaankhuu ; freebsd-current@freebsd.org
> Sent: Tue, July 13, 2010 11:04:59 AM
> Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
>
> PseudoCylon wrote:
> > - Original M
- Original Message
> From: Hans Petter Selasky
> To: freebsd-current@freebsd.org
> Cc: Andrew Thompson ; Sam Leffler ;
>PseudoCylon ; freebsd-...@freebsd.org
> Sent: Mon, July 12, 2010 2:01:11 PM
> Subject: Re: [panic] Race in IEEE802.11 layer towards device driv
- Original Message
> From: PseudoCylon
> To: Ganbold Tsagaankhuu
> Cc: Ganbold ; freebsd-current@freebsd.org
> Sent: Tue, July 6, 2010 12:26:58 AM
> Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
>
> >>>>>> From: Ganbold
> >
- Original Message
> From: Hans Petter Selasky
> To: freebsd-current@freebsd.org
> Cc: Andrew Thompson ; Sam Leffler ;
>PseudoCylon ; freebsd-...@freebsd.org
> Sent: Mon, July 12, 2010 2:01:11 PM
> Subject: Re: [panic] Race in IEEE802.11 layer towards device driv
- Original Message
> From: Hans Petter Selasky
> To: freebsd-current@freebsd.org
> Cc: PseudoCylon ; Ganbold Tsagaankhuu
>; Ganbold
> Sent: Tue, July 6, 2010 12:54:31 AM
> Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
>
Hello
PseudoCylon is he
>>>>>> From: Ganbold
>>>>>> To: PseudoCylon
>>>>>> Cc: freebsd-current@freebsd.org; Ganbold Tsagaankhuu
>>>>>> Sent: Wed, June 16, 2010 6:33:47 AM
>>>>>> Subject: Re: CALL for TEST [HOSTAP] run(4) ralin
>>>> From: Ganbold
>>>> To: PseudoCylon
>>>> Cc: freebsd-current@freebsd.org; Ganbold Tsagaankhuu
>>>> Sent: Wed, June 16, 2010 6:33:47 AM
>>>> Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
>>>>
>>
- Original Message
>> From: Ganbold
>> To: PseudoCylon
>> Cc: freebsd-current@freebsd.org; Ganbold Tsagaankhuu
>> Sent: Wed, June 16, 2010 6:33:47 AM
>> Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
>>
>> AK-san,
>
>Pse
- Original Message
> From: Ganbold
> To: PseudoCylon
> Cc: freebsd-current@freebsd.org; Ganbold Tsagaankhuu
> Sent: Tue, June 15, 2010 8:02:02 AM
> Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
>
> AK-san,
>PseudoCylon wrote:
>&
>>> From: Ganbold
>>> To: PseudoCylon
>>> Cc: freebsd-current@freebsd.org; Ganbold Tsagaankhuu
>>> Sent: Thu, June 10, 2010 10:53:30 AM
>>> Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
>>>
>>> It seems like i
- Original Message
> From: Hans Petter Selasky
> To: PseudoCylon
> Cc: freebsd-...@freebsd.org; freebsd-current@freebsd.org
> Sent: Sat, June 12, 2010 12:30:18 AM
> Subject: Re: run(4) patch
>
>> On Friday 11 June 2010 08:27:53 PseudoCylon wrote:
>> Hel
- Original Message
> From: Ganbold
> To: PseudoCylon
> Cc: freebsd-current@freebsd.org; Ganbold Tsagaankhuu
> Sent: Thu, June 10, 2010 10:53:30 AM
> Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
>
> It seems like it is running without any problem
> Hello,
>
> Sorry for taking long.
>
> But, please try following update (if_run.c and if_runvar.h)
> http://gitorious.org/run/run/blobs/raw/a74fa9ba5a16f1d1f058efa724261351e267a474/dev/usb/wlan/if_run.c
> http://gitorious.org/run/run/blobs/raw/a74fa9ba5a16f1d1f058efa724261351e267a474/dev/usb/wlan/
- Original Message
> From: Ganbold
> To: PseudoCylon
> Cc: freebsd-current@freebsd.org; Ganbold Tsagaankhuu
> Sent: Wed, June 9, 2010 9:09:22 AM
> Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
>
> Any update on driver side?
> Please
- Original Message
> From: Ganbold
> To: PseudoCylon
> Cc: freebsd-current@freebsd.org; Ganbold Tsagaankhuu
> Sent: Wed, May 26, 2010 10:10:46 AM
> Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
>
> It looks like either bridge or wlan/run drive
- Original Message
> From: Hans Petter Selasky
> To: freebsd-current@freebsd.org
> Cc: Ganbold ; PseudoCylon ;
> Ganbold Tsagaankhuu
> Sent: Wed, May 5, 2010 2:00:02 PM
> Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
>
> Hi,
>
> Ca
- Original Message
> From: Ganbold
> To: PseudoCylon
> Cc: freebsd-current@freebsd.org; Ganbold Tsagaankhuu
> Sent: Mon, May 3, 2010 8:54:11 AM
> Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
>
> Thanks a lot, works no problem so far here wi
- Original Message
> From: Ganbold
> To: PseudoCylon
> Cc: freebsd-current@freebsd.org; Ganbold Tsagaankhuu
> Sent: Sun, April 25, 2010 1:44:20 AM
> Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
>
> Thank you very much.
> However it still pa
Hello,
Thank you for all the info.
This one shall work.
http://projects.nasreddine.com/projects/run/repository/revisions/mips_fix/show/dev/usb/wlan
Please update if_run.c and if_runvar.h (2 files).
Just in case, after kldload, please issue
# sysctl hw.usb.run.debug=1
Now it prints out very little
Hello,
Can you try this? (all 3 files has been updated)
http://projects.nasreddine.com/projects/run/repository/revisions/mips_fix/show/dev/usb/wlan
This is for rev 207077 or newer.
If you are using older rev, please let me know with rev #, I'll change the code
accordingly.
If it isn't too much
AK
- Original Message
> From: Ganbold
> To: PseudoCylon
> Cc: freebsd-current@freebsd.org
> Sent: Tue, April 6, 2010 7:29:16 AM
> Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
>
> PseudoCylon wrote:
> - Original Message
>
>
&
- Original Message
> From: Ganbold
> To: PseudoCylon
> Cc: freebsd-current@freebsd.org
> Sent: Wed, March 31, 2010 8:08:29 AM
> Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
>
> Does stock run(4) support hostap mode yet?
No. There were some bugs
- Original Message
> From: Ganbold
> To: PseudoCylon
> Cc: freebsd-current@freebsd.org
> Sent: Sat, March 27, 2010 7:01:32 AM
> Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
>
> JFYI, I have just tested if_run and works fine on HEAD (i386).
>
>> Same.
>>
>> rspro# ifconfig wlan0 up
>>
>> rspro# Trap cause = 5 (address error (store) - kernel
> mode)
>> [ thread pid 0 tid 100047 ]
>> Stopped at
> ieee80211_radiotap_vdetach+0x70:
> sh v1,0(a0)
>> db> bt
>> Tracing pid 0
> tid 100047 td 0xc0f1f260
>> db_trace_t
Can you show me output of followings? (I have only intel chips.)
#kldstat | grep if_run (after loading the driver. no need to run it)
#objdump -h /boot/kernel/if_run.ko | grep text
#objdump --source /boot/kernel/if_run.ko | grep \>:
AK
> Same.
> rspro# ifconfig wlan0 up
>
> rspro# Trap ca
Hello, again.
Can you try this patch? Patch is for if_runvar.h
--begin patch--
*** old_if_runvar.h2010-03-16 19:14:25.0 -0600
--- new_if_runvar.h2010-03-16 19:15:51.0 -0600
***
*** 184,186
uint8_tval;
! }bbp[8], rf[10];
Hello,
Can you check version of firmware for me?
At the end of ralink's license (before the actual code) in rt2870.fw.uu, if it
says
RT2870 v. 0.11
RT3071 v. 0.11
it's the latest. If there is no version info, it is old version.
Your chipset, rt3070 + rf3020 uses mcu command to select the antenn
- Original Message
> From: Rui Paulo
> To: Weongyo Jeong
> Cc: PseudoCylon ; Alexander Egorenkov
> ; freebsd-current@freebsd.org
> Sent: Fri, March 12, 2010 7:42:46 PM
> Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
>
> On 13 Mar 2010, at 09
- Original Message
> From: Rui Paulo
> To: PseudoCylon
> Cc: freebsd-current@freebsd.org
> Sent: Thu, March 4, 2010 5:02:50 PM
> Subject: Re: CALL for TEST [HOSTAP] run(4) ralink usb wireless
>
> Hi,
>
>
> This code is fine from a quick review. It just
Hello,
Finally, I have fixed mysterious device lock out and run(4) works fine in
HOSTAP mode. Up time is 80 hours and counting. I even filed tax though it.
The device supports up to 253 stations. I only tested with 2 station. If you
have resources, please hit it with bunch of STAs.
As usual co
Hello,
There are revisions on OpenBSD run(4), so I applied the applicable changes to
ours.
Because lots of changes has been made (more than 20 revisions in 24 hour
period), I thought I should do a quick test.
Please give it a try. The driver is posted at
http://forums.freebsd.org/showpost.php?
49 matches
Mail list logo
