<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 20, 2016 at 6:42 PM, Chris Johns <span dir="ltr"><<a href="mailto:chrisj@rtems.org" target="_blank">chrisj@rtems.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 21/04/2016 9:01 AM, Joel Sherrill wrote:<br>
> Console/Printk Device Selection<br>
> ===============================<br>
> @@ -19,9 +19,9 @@ in the following order of priority:<br>
> + VGA and keyboard<br>
> + COM1 through COM4aaa<br>
><br>
> What is the aaa?<br>
><br>
<br>
</span>No idea, must have been cat on the keyboard.<br>
<span class=""><br>
> +<br>
> + if (comma) {<br>
> + option = comma + 1;<br>
> + baudrate = strtoul(option, 0, 10);<br>
> + switch (baudrate) {<br>
> + case 115200:<br>
> + case 57600:<br>
> + case 38400:<br>
> + case 19200:<br>
> + case 9600:<br>
> + case 4800:<br>
> + port->pDeviceParams = (void*) baudrate;<br>
> + BSPBaseBaud = baudrate; /* REMOVE ME */<br>
> + break;<br>
> + default:<br>
> + printk("invalid option (--gdb): bad baudrate\n");<br>
> + return;<br>
> + }<br>
> + }<br>
><br>
><br>
> Is there anyway the code parsing this option can be shared with that<br>
> for the com ports?<br>
<br>
</span>Yes that could be done but I do not think so for this patch set. This is<br>
in code in shared/comm and the BSP code needs to be reorganised.<br>
<br>
Given the conversation with Sebastian about consoles this BSP needs some<br>
rework. Maybe this can happen then.<br>
<span class="HOEnZb"><font color="#888888"><br></font></span></blockquote><div>I am ok with letting it go. Opportunities for shared code have to be noted or</div><div>they never happen.</div><div><br></div><div>Fix the cat scratches and commit. :)</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="HOEnZb"><font color="#888888">
Chris<br>
</font></span></blockquote></div><br></div></div>