Re: boot2/loader: serial port handling

From: George Neville-Neil <gnn_at_neville-neil.com>
Date: Fri, 19 Oct 2012 17:31:54 -0700
On Oct 18, 2012, at 14:48 , Doug Ambrisko <ambrisko_at_ambrisko.com> wrote:

> On Fri, Oct 12, 2012 at 05:13:47PM -0700, Garrett Cooper wrote:
> | On Fri, Oct 12, 2012 at 5:09 PM, Xin Li <delphij_at_delphij.net> wrote:
> | > -----BEGIN PGP SIGNED MESSAGE-----
> | > Hash: SHA256
> | 
> | ...
> | 
> | > Ah I wish I am not this far behind my email backlog.  Yes I think
> | > these (241300 and 241301) will solve the problem.
> | 
> |     Yeah -- forgot about the other one. There's another enhancement
> | that would make this even better (apart from maybe having multiple
> | primary consoles): setting the primary console if present and having
> | fallbacks in the event that the original primary wasn't set or
> | configurable; it was a thing that was present in another project I
> | worked on with sio that was pretty slick (and I think that there would
> | be some parties who wouldn't mind if the same was done with uart(4)).
> 
> This concept was objected to when I checked it into sio(4) so I had
> to back it out.  Some liked it.  I have ported it to uart(4) since we
> need that functionality when we moved to a newer FreeBSD.

BTW, sorry to come in late on the thread.  Would this cause the loader
to reset the machine?  On a box in my work testlab I have not
been able to use a recent /boot/loader for a few weeks.

I get to the BIOS drive C: is disk0                                                          

bit and BOOM.

Best,
George
Received on Fri Oct 19 2012 - 22:32:03 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:31 UTC