POMdev wrote:
> my docker build system is finally working, and I am working on modifying
> or reverting a later wireless chip driver (version 063) to support the
> existing AR6002 chip in the radios (driver now 062). The other important
> pieces of the wireless 'stack' have been built and
yep all is well. Community firmware installed
mamema's Profile: http://forums.slimdevices.com/member.php?userid=44662
View this thread: http://forums.slimdevices.com/showthread.php?t=114123
ralphy wrote:
> If the updated wpa_supplicant software for the radio is causing too many
> problems, then lets consider reverting to the version included with
> stock.
>
> I can continue to use v2.9 regardless.
I'll lodge an issue on your github site, which will (hopefully) lay out
everything
mrw wrote:
> ...I shall add that later versions of the wpa_ software (i.e. as
> included in the Radio's community firmware release) bring their own
> problems/incompatibilities with the way SqueezePlay has been brought up
> to expect. Not insuperable, I think (I have yet to relay one issue to
>
Now i have this. :-) After i reinstalled the offered firmware 7.7.ish to
look what happens.
Installed now the community firmware plugin in LMS and waiting, that the
8.x is offered.
mamema's Profile:
mamema wrote:
> Now i have this. :-) After i reinstalled the offered firmware 7.7.ish to
> look what happens.
> Installed now the community firmware plugin in LMS and waiting, that the
> 8.x is offered.
Have you ticked the box?
33748
mrw wrote:
> I shall add that later versions of the wpa_ software (i.e. as included
> in the Radio's community firmware release) bring their own
> problems/incompatibilities with the way SqueezePlay has been brought up
> to expect. Not insuperable, I think (I have yet to relay one issue to
>
POMdev wrote:
>
> Sounds interesting. How is this done?
Settings|Advanced|Logging, like any other Squeezeplay logging. Im
assuming that you have become acquainted with it over the last few
months. net.socket is the relevant log category.
mrw wrote:
> Settings|Advanced|Logging, like any other Squeezeplay logging. Im
> assuming that you have become acquainted with it over the last few
> months. net.socket is the relevant log category.
Thanks, I'll check it out. No, I am working on the os level using the
TTL serial port, ssh,
gordonb3 wrote:
>
> SIGN CHANGE
> There is a difficult way and a simple way to address this. The problem
> with the simple way is that this requires the jive executable to be
> recompiled and therefore this is not a simple patch. The difficult and
> user patchable way is to handle the sign
Steevee28 wrote:
> Are you able to edit the jive_jiffies() function in src/common.h to
> return a timer value right from the start that is - let's say - 1 minute
> before wrapping (corresponding to 0x7FFF15A0) ? (...)
>
@gordonb3: Oh, take care, one minute may be too short to be able to
Oh Christ...
I'm going about this all the way wrong. I was focussing on matching the
numbers inside the LUA scripts, patching the code to be indifferent to
the sign change, but the whole point of this jive_jiffies() thing is for
all independent components to have their time values synchronized.
naguirre wrote:
> ...Setting up an ubuntu 10.04 is not so easy these days, so i setup a
> Docker for it. You can find it here with few more fixes.
> https://github.com/naguirre/squeezeos/tree/dev/nae/docker
This was not working for me for the longest time. I was getting the
following error:
13 matches
Mail list logo
