For more info on setting up a bridged access point, see here.

Since #379 is a bit old, and it's technically limited to a Bridged config option during installation, I'm opening this issue as a starting point. I am working on an easy way to toggle to Bridged

I am trying to add additional IEs to the beacon/probe resp frames on a PI 3B+ using nexmon. I'm having difficulty understanding how these frames get configured.

I gather the frames come in from hostapd into cfg80211.c, which pulls out selected IEs and passes them from the brcmfmac driver, using string commands like arp_ol and ndoe, across an interface (dbus?) to the firmware, which reassembles

In this page :
https://github.com/opencardev/crankshaft/wiki/Building-the-binary-blobs

This url is 404 :
Please refer to https://github.com/htruong/crankshaft/blob/master/COMPILE.md to start.

Maybe I'll need more help on how to build crankshaft, can you please elaborate on how to build.

Thanks

The wifi connect container runs systemd, which requires it to be privileged. This should be documented.

crossdev --stable -t aarch64-unknown-linux-gnu -oO /usr/local/portage-crossdev
...
distcc-vm ~ # gcc-config --list-profiles
[1] aarch64-unknown-linux-gnu-9.2.0 *
[2] x86_64-pc-linux-gnu-9.2.0 *

demouser@pi64 ~ $ gcc-config --list-profiles
[1] aarch64-unknown-linux-gnu-9.3.0 *

is there a paticular reason the wiki isn't giving

crossdev -t aarch64-unknown-linux-gnu -o

When I apply textures to built-in procedural objects(cube, sphere, torus, billboard etc.) they display OK, but when the model is loaded from .obj, this happens:

![bug_002](h

In the PINN documentation, when it gets to the section "How to customize an OS install", it doesn't give much detail; it just points the reader to the noobsconfig documentation. I think it would be easier to follow if the relevant information was integrated into the PINN documentation instead.

As it is, both documents seem to say that noobsconfig is obsolete, that its functionality is integrat

We should do it !

Where is the best place ? Webui ? Log files ? Wiki ?
All of the above ?

Some limits are imposed by the protocol,

some are imposed by kernel defaults (like spi max transfer size )

Some are based on the arduino ram / sketch used

this conversion can be done on the fly.
document it and/or maybe provide a script that can be downloaded and ran

something along the lines of:

cd /tmp
curl -L https://api.cattlepi.com/images/global/raspbian-lite/2018-06-29/bootstrap/cattlepi.zip?apiKey=deadbeef > cattlepi.zip
unzip cattlepi.zip
mkdir -p /tmp/boot
sudo mount  -o loop,offset=1048576 /tmp/cattlepi.img /tmp/boot
su

the plan is to develop on top of the Mopidy javascript library.

it will be great to integrate the LED matrix APIs so a user could draw on it directly from the same web-interface (or maybe the we could get more ambitio