New oleg firmware version

[sebw]

Hi lly

Many thanks for including my sound card (041e:3048) in the r256 unmute patch.
I shall try it out in the next day or two.

Just to confirm that I now have my sound card running unmuted across USB 2.0 using 1.9.2.7-d-r256 on my WL500gx.

Many thanks.

[wpte]

hey lly

would it be possible to set the default regulatory mode in the wireless advanced tab (for wl-500w routers) to 802.11h?
since it's something all the intel cards use and most other wireless cards to get a faster speed than 54mbit.

802.11h is also newer plus it's used in draft-N 2.0 (with the 5GHz band):

http://en.wikipedia.org/wiki/IEEE_802.11h
http://en.wikipedia.org/wiki/IEEE_802.11d

to set it to H I think most people will stick with oleg because they won't notice any difference with original firmware on wireless speeds (since most of them don't look to advanced settings).

thanks

[lly]

would it be possible to set the default regulatory mode in the wireless advanced tab (for wl-500w routers) to 802.11h?

we will try to do that.

[sebw]

I am having trouble using my webcam which worked under 1.9.2.7-10 F/W.
I am using Palantir.
I have modprobed the pwc and pwcx modules but get the following:

dmesg output...

Linux video capture interface: v1.00
pwc Philips webcam module version 9.0.2 loaded.
pwc Supports Philips PCA645/646, PCVC675/680/690, PCVC720[40]/730/740/750 & PCVC830/840.
pwc Also supports the Askey VC010, various Logitech Quickcams, Samsung MPC-C10 and MPC-C30,
pwc the Creative WebCam 5 & Pro Ex, SOTEC Afina Eye and Visionite VCS-UC300 and VCS-UM100.
usb.c: registered new driver Philips webcam
pwc Logitech QuickCam 4000 Pro USB webcam detected.
pwc Registered as /dev/video0.
pwc Philips webcam decompressor routines version 9.0-BETA-2
pwc Supports all cameras supported by the main module (pwc).
pwc Adding decompressor for model 645.
pwc Adding decompressor for model 646.
pwc Adding decompressor for model 675.
pwc Adding decompressor for model 680.
pwc Adding decompressor for model 690.
pwc Adding decompressor for model 720.
pwc Adding decompressor for model 730.
pwc Adding decompressor for model 740.
pwc Adding decompressor for model 750.

Palantir ouput....

$ Apr 24 11:47:31 [config] Ignoring deprecated `Audio' directive at line 67
Apr 24 11:47:31 [main] -- palantir 2.7 starting --
Apr 24 11:47:31 [main] Definitions for 1 devices found
Apr 24 11:47:31 [main] No serial port specified
Apr 24 11:47:31 [main] No named pipe specified
Apr 24 11:47:31 [video] Card:   Logitech QuickCam Pro 4000 (/dev/v4l/video0)
Apr 24 11:47:31 [video] Capabilities:   1 (capture )
Apr 24 11:47:31 [video] Size:   (160x120)-(640x480)
Apr 24 11:47:31 [video] Channel no. 0 ('Webcam')        tuners: 0, flags: 0, type: 2, norm: 10937
Apr 24 11:47:31 [video] Unmuted audio input 0
Apr 24 11:47:31 [video] Audio input 0 does not support volume control
Apr 24 11:47:31 [video] RGB palette unavailable.
Apr 24 11:47:31 [video] trying YUV420P...
Apr 24 11:47:31 [video] brightness: 32768  hue: 65535  colour: 32768
Apr 24 11:47:31 [video] contrast: 32768  whiteness: 32768
Apr 24 11:47:31 [video] depth: (24)  palette: 15
Apr 24 11:47:31 [video] Actual capture box is 320x240 (requested 320x240)
Apr 24 11:47:31 [video] Camera has no pan/tilt control
Apr 24 11:47:31 [video] Frame rate set to 15 f/s
Apr 24 11:47:31 [video] Video buffer size: 921600, frames: 2
Apr 24 11:47:31 [video] Allocating yuv->rgb buffer (230400 bytes)
Apr 24 11:47:31 [main] Starting device thread
Apr 24 11:47:31 [audio] Setting up audio device /dev/sound/dsp1
Apr 24 11:47:31 [audio] Audio sample rate set to 8000 Hz
Apr 24 11:47:31 [audio] Audio input buffering: 4 fragments of 256 bytes each
Apr 24 11:47:31 [main] Listening on 0.0.0.0 port 3000
Apr 24 11:47:31 [main] Listening on 0.0.0.0 port 3001
Apr 24 11:47:31 [main] Control queue timeout set to 30 s

Palantir output following client connection....

Apr 24 12:09:32 [main] 192.168.0.1 - #0: connection accepted, spawning server.
Apr 24 12:09:32 [main] 1 client(s) connected
Apr 24 12:09:32 [main] Capture thread started
Apr 24 12:09:32 [http] 192.168.0.1 - video server started
Apr 24 12:09:32 [http] 192.168.0.1 - requested URL `/'
Apr 24 12:09:32 [http] 192.168.0.1 - User-Agent: pclient/ack 2.4 [1] (Win32)
Apr 24 12:09:32 [http] 192.168.0.1 - streaming mode: continuous, closed loop

back to dmesg output....

pwc Failed to set LED on/off time.
pwc set_video_mode(176x144 @ 10, palette 15).
pwc decode_size = 1.
pwc Using alternate setting 1.
hcd.c: use explicit queuing not urb->next
pwc isoc_init() submit_urb 0 failed with error -22
hcd.c: use explicit queuing not urb->next
pwc isoc_init() submit_urb 1 failed with error -22
pwc set_video_mode(320x240 @ 15, palette 15).
pwc decode_size = 3.
pwc Using alternate setting 4.
hcd.c: use explicit queuing not urb->next
pwc isoc_init() submit_urb 0 failed with error -22
hcd.c: use explicit queuing not urb->next
pwc isoc_init() submit_urb 1 failed with error -22

The client shows no picture and top shows no CPU load for Palantir.
I presume the problem is to do with the error -22 which occurs in the pwc-if.c module.
Any suggestions or help would be appreciated.

[lly]

I am having trouble using my webcam which worked under 1.9.2.7-10 F/W.
...
I presume the problem is to do with the error -22 which occurs in the pwc-if.c module.
Any suggestions or help would be appreciated.

This is due to updated kernel code.

Updated:
I was wrong - pwc 10.0.12-rc1 isn't compatible with 2.4 kernels [ At least, urb->next don't used in it. ]

Problems similar to this, present in most old webcam drivers For example - https://dev.openwrt.org/ticket/532
We will try to fix this issue, but I can't you promise exact date when it happens.

[sebw]

Should I enter this pwc issue here: http://code.google.com/p/wl500g/issues/list

[lly]

Should I enter this pwc issue here: http://code.google.com/p/wl500g/issues/list

As you wish. People from russian forum discover this bug a few weeks ago. I didn't put this link here since most of people in this thread don't understand russian language.

Unfortunately, webcam developers switched to 2.6 trunk several years ago, so we have to backport much things from new kernels, and this job is not so easy...

[teddy_bear]

would it be possible to set the default regulatory mode in the wireless advanced tab (for wl-500w routers) to 802.11h?

AFAIK 802.11h disables connectivity for Intel 2200BG and similar wireless cards (by setting the spectrum management flag to ON), so it's probably a good idea to keep regulatory mode "off" by default.

Alternatively wlconf can be patched to keep spectrum management off even if regulatory is set to "h" - but I don't know if this change may have any other implications...

[wpte]

AFAIK 802.11h disables connectivity for Intel 2200BG and similar wireless cards (by setting the spectrum management flag to ON), so it's probably a good idea to keep regulatory mode "off" by default.

Alternatively wlconf can be patched to keep spectrum management off even if regulatory is set to "h" - but I don't know if this change may have any other implications...

well yes, spectrum management is one of the key good features of 802.11h... less intefierence

but by default the regulatory mode is set to 802.11d, wich isn't that great imo
I didn't have any problems with B/G cards with 802.11h tho

[teddy_bear]

I didn't have any problems with B/G cards with 802.11h tho

Not sure... I don't have any Intel 2200BG card to test it myself, so this info is mostly based on this OpenWRT ticket, and this Tomato thread. Also, Oleg recommended to set mode to "d" when he releazed 1.9.2.7-8 - specifically to "solve some problems with Intel WiFi cards".

But what I know for a fact, is that the Atheros wl card in my notebook works better when regulatory mode is "off" - otherwise it keeps reconnecting all the time...

I'd vote for "off" as a default value, since according to the above and what I could google out, it causes less problems with various wifi clients than "d" or "h" modes. Anyway - not a big deal, the option is still available and can be set to "h" if that works better for you .

[theMIROn]

I'd vote for "off" as a default value

+1, completely agree

[wpte]

a bit offtopic, but:
I completed my own firmware compiles successfully thanks to the wiki on googlecode

Now can I use "export PATH=$PATH:/opt/brcm/hndtools-mipsel-uclibc/bin" for other projects to cross compile?

since I'm trying to get the master make file to work... but the openwrt svn is offline so it wont complete