From: Daryl Van Humbeck <dvanhumb@sfu.ca>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: serial port
Date: Sun, 18 Nov 2007 23:18:30 -0800 [thread overview]
Message-ID: <474138C6.3070508@sfu.ca> (raw)
In-Reply-To: <47402C4B.20907@nic.fi>
[-- Attachment #1: Type: text/plain, Size: 1749 bytes --]
Vesa Jääskeläinen wrote:
> Robert Millan wrote:
>
>> On Sun, Nov 18, 2007 at 12:33:00PM +0100, Marco Gerards wrote:
>>
>>> Robert Millan <rmh@aybabtu.com> writes:
>>> Perhaps because the serial command sets it up? Although I agree it
>>> seems a bit weird that it works this way. Perhaps it should be
>>> enabled with the same defaults from the beginning?
>>>
>>> One problem of initializing it is that hardware will be accessed,
>>> while it might not be desirable.
>>>
>> Maybe we could move this to grub_term.init ? This way hardware is not
>> accessed untill user requests a switch.
>>
>
> This is the same way it works with gfxterm. You define video mode
> beforehand of the switch.
>
> But there is actually a one architectual issue here... How are we going
> to support graphical terminal and serial terminal at the same time? eg.
> allow user to enable multiple terminals...
>
>
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
Just thought I'd put my two cents in to this discussion, I'm not really
planning on contributing code to Grub 2, though I might help stimulate
discussion...
If you wanted to enable both serial and graphical terminals (or any
other kind(s) of terminals, just that there are more than one enabled at
once), you'd really have to switch to using the Model/View/Controller
architecture for user interaction.
However there is also the difficulty that when you have two separate
terminals into the same session (or whatever else you want to think of),
that might become a security issue.
Just my two cents on this matter.
Hope this helps (though it might not),
Daryl Van Humbeck.
[-- Attachment #2: Type: text/html, Size: 2476 bytes --]
next prev parent reply other threads:[~2007-11-19 7:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-10 21:31 serial port Robert Millan
2007-11-18 11:33 ` Marco Gerards
2007-11-18 11:56 ` Robert Millan
2007-11-18 12:12 ` Vesa Jääskeläinen
2007-11-18 12:24 ` Robert Millan
2007-11-18 12:41 ` Marco Gerards
2007-11-18 12:32 ` Marco Gerards
2007-11-18 12:43 ` Vesa Jääskeläinen
2007-11-19 7:18 ` Daryl Van Humbeck [this message]
2007-11-19 17:13 ` Vesa Jääskeläinen
2007-11-18 12:14 ` Marco Gerards
-- strict thread matches above, loose matches on Subject: below --
2021-02-11 11:22 Serial Port Leandro Bucci
2021-02-11 12:52 ` Philippe Gerum
2005-02-17 7:41 serial port Tim Newsham
2005-02-18 1:36 ` Tim Newsham
2004-07-24 15:11 serial port read working but not write Jan-Benedict Glaw
2004-08-03 17:41 ` Serial port suresh shenoy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=474138C6.3070508@sfu.ca \
--to=dvanhumb@sfu.ca \
--cc=grub-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.