On 11/03/2016 11:49, Joel Sherrill wrote:
On Thu, Mar 10, 2016 at 6:42 PM, Chris Johns <chr...@rtems.org <mailto:chr...@rtems.org>> wrote: On 10/03/2016 09:25, Joel Sherrill wrote: This was used to open, write, and close the VGA console and /dev/pcicom1 for testing purposes. Does this do the same thing? [/] # dd if=text.txt of=/dev/pcicom1 I didn't mean to submit this. It was a test command so I could very explicitly control calling open(), write(), and close(). I had debug printk's turned on to see the register accesses for each.
Best to keep as an example.
That functionally does the same operations if you had a set of small files but you wouldn't see a break between open(), write() and close().
Files are easy to create and add to the root fs. There should be some in /etc.
I don't know if it is worth being in the tree or not. It was a quickly thrown together utility for testing. If it has value, then we can rename it and add some requirements.
I say out of the tree. Commands are easy to add and difficult to remove.
My lspci command is similar. If we get every BSP to standard PCI support, it might be useful but until then, it is just a test utility.
This is useful. If it is not present someone will just invent it again. The doco needs to be added to docs repo. The shell doco source is ok to change. :)
Chris _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
