what is the 'minimal clean' needed before building another image.Īny tips or insights on what else to verify/test next would be appreciated. what steps can I bypass when recompiling each image ? Obviously skipping the toolchain will save enormous amounts of time.figure out the next build/testing feedback loop should be:.Identify the sizing required for the image (will probably follow similar convention to in 7362.finish verifying all devices get detected.Any suggestions on how to verify devices are detected before I bite the bullet and flash an image? Suggestions on any other useful modules to include in the kernel ramfs image to aid testing/validation? memory only showing as 128Mb, I will need to expand to fill/use the full 256 (or 512, I have found conflicting information in my research).the physical 'Lan3' connector never reports a link at all (also confirmed no link established with crossover cable and my PC directly connected.'eth0 port 1 = the physical 'Lan4' connector.'eth0 port 2' = the physical 'Lan2' connector.'eth0 Port 4' = the physical 'Lan1' connector on back of device.

tailing dmesg shows the following when I disconnect/reconnect ethernet cable: ethernet physical ports are a bit weird.i w list isn't showing any output (not sure if this is normal for a minimal kernel ramfs image).The bad (where I need to focus my efforts) I can happily report that the 7362 kernel ramfs booted successfully on my 7490. Bare with me, as this is the first device I've attempted to add support for.Īs a starting point, I am beginning on the excellent work of (which is still being finalized before merge to master). Well, I thought I'd give it a try and see if I could do this myself.

Fritz box 7490 usb drucker android