On Tue, Oct 23, 2012 at 09:35:26AM -0700, Tim Bird wrote: > Also, I use 'git format-patch' quite a bit when I'm converting > from git commits to a quilt series. I know people use this > for submitting patches to mainline, but I use it a bit differently > (I think) when I'm making a quilt patch series.
We have a nice git+quilt feature in ptxdist: - You can configure a switch to extract quilt series into git repositories: that way ptxdist extracts a tar ball, checks the initial state into a git repository and applies the quilt series with git. - If you hack on a component, just use git the way it is usually used. - When you are ready, ptxdist has automatically added a new command 'git ptx-patches' into that repository, which beams the current patch series from git back into a quilt series in ptxdist. - While doing so, it removes the git version (so that you don't get changes in the patches when different people use different git versions) and it removes the sha sums. Very convenient, if you use ptxdist :-) > Do you have any custom tool that you use to solve a particular > problem you run into frequently, that you would be willing to > describe? genimage: create flash/sd/hd images http://www.pengutronix.de/software/genimage/download/ memedit: hack your memory mapped registers http://www.pengutronix.de/software/memedit/downloads/ ptx_ts: timestamp your <anything> http://www.pengutronix.de/software/ptx_ts/index_en.html > 3. development practices: Mostly printk as well. With ptxdist, you can build your BSP for a qemu based platform instead of the real target, which makes it easy to hack on anything but the kernel without going onto the target. > 3. hardware configuration > How is your hardware set up? The first thing I do when I get a > new board is set it up with a network connection and serial connection > to my host (on an isolated network segment, of course, since Sony doesn't > like my host acting like a DHCP server for other machines!). Same here; we have a separate lab net for that, with the big compile machines having access to it as well :) > Also, I use a digital loggers web-controllable power switch. I used > all kinds of different things previously (including relays that could > toggle reset buttons on the boards, or control the power to the board > via a USB power switch). These are in the PTX remotelabs (the 19" ones): http://www.gude.info/index.php?lng=1§ion=products&product=epcalg > 4. testing > Do you use a specific tool for testing? I have a simple script called > 'tbtorture.sh' that I used to 'hammer' my board when I trying to stress > it. (Lately, I've been trying to cause stack overflows on my ARM system > with 4K stacks.) tbtorture is my own tool that I wrote based on > 'do_hell' by Ingo Molnar. Unfortunately, Sony's internal distribution > doesn't have all the programs that do_hell called, and I re-wrote > parts of it to correspond to what we have in our distro (pretty > much just busybox and a few other things.) We basically have 'ptxdist test <testscript>' which is a remote control mechanism in ptxdist which gives you access to the target via - ssh - rsh (with urshd, which is realtime-aware) - serial - serial-over-ethernet (Moxa) The core mechanism is scripted in kermit, but the actual test scripts are plain shell code. You can run shell commands on the test host and on the target, and you can basically do anything with the test results. rsc -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 | _______________________________________________ Celinux-dev mailing list Celinux-dev@lists.celinuxforum.org https://lists.celinuxforum.org/mailman/listinfo/celinux-dev
