From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1fO1Xr-0002zj-HQ for mharc-grub-devel@gnu.org; Wed, 30 May 2018 09:53:43 -0400 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54847) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fO1Xp-0002xb-6c for grub-devel@gnu.org; Wed, 30 May 2018 09:53:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fO1Xl-0003HF-9j for grub-devel@gnu.org; Wed, 30 May 2018 09:53:41 -0400 Received: from boksu.net-space.pl ([185.15.1.105]:43239) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_3DES_EDE_CBC_SHA1:24) (Exim 4.71) (envelope-from ) id 1fO1Xk-0003GQ-Ub for grub-devel@gnu.org; Wed, 30 May 2018 09:53:37 -0400 Received: (from localhost user: 'dkiper' uid#4000 fake: STDIN (dkiper@boksu.net-space.pl)) by router-fw-old.local.net-space.pl id S1841712AbeE3Nxe (ORCPT ); Wed, 30 May 2018 15:53:34 +0200 Date: Wed, 30 May 2018 15:53:34 +0200 From: Daniel Kiper To: Petter Gustad Cc: grub-devel@gnu.org, amworsley@gmail.com, dkiper@net-space.pl Subject: Re: FTDI serial console support? Message-ID: <20180530135334.GK27874@router-fw-old.local.net-space.pl> References: <20180518115555.GB13069@router-fw-old.local.net-space.pl> <20180518.163239.1042395263713665873.petter@gustad.com> <20180526.072124.1040471540849972102.petter@gustad.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180526.072124.1040471540849972102.petter@gustad.com> User-Agent: Mutt/1.3.28i X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 185.15.1.105 X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 May 2018 13:53:42 -0000 On Sat, May 26, 2018 at 07:21:24AM +0200, Petter Gustad wrote: > From: Andrew Worsley > Subject: Re: FTDI serial console support? > Date: Sat, 19 May 2018 23:12:42 +1000 > > > On 19 May 2018 at 00:32, Petter Gustad wrote: > >> From: Daniel Kiper > >> Subject: Re: FTDI serial console support? > >> Date: Fri, 18 May 2018 13:55:55 +0200 > >> > >>> On Fri, May 18, 2018 at 01:01:41PM +0200, Petter Gustad wrote: > >>>> From: Daniel Kiper > >>>> Subject: Re: FTDI serial console support? > >>>> Date: Wed, 16 May 2018 11:32:19 +0200 > >>>> > >>>> > On Wed, May 16, 2018 at 06:21:17AM +0200, Petter Gustad wrote: > >>>> >> From: Daniel Kiper > >>>> >> Subject: Re: FTDI serial console support? > >>>> >> Date: Tue, 15 May 2018 22:00:06 +0200 > >>>> >> > >>>> >> > On Fri, May 11, 2018 at 03:55:36PM +0200, Petter Gustad wrote: > >>>> >> >> > >>>> >> >> Is there a way to specify a FTDI based serial console using > >>>> >> >> GRUB_TERMINAL, GRUB_SERIAL_COMMAND, or some other variable? If yes, > >>>> >> >> what is the syntax? > >>>> >> >> > >>>> >> >> BTW my serial port adapter matches the vendor id and device id given > >>>> >> >> in grub-core/bus/usb/serial/ftdi.c: > >>>> >> >> > > .... > >>> Could you just do "insmod usbserial_ftdi"? There is a chance that it > >>> will pull in all needed dependencies without breaking disk access. > >> > >> Thanks. Only "insmod usbserial_ftdi" does work in the sense that it > >> will not break disk access. I also managed to load grub using PXE/tftp > >> where I was not dependend upon disk access. > >> > >> But in both cases it does not work like in the coreboot URL above. > >> After do insmod on usbserial_ftdi and usbserial_usbdebug the > >> terminal_output command will only return console as its active output > >> terminal. It will list serial_* as available output terminals, but I > >> can't select usb0, usb1, etc as argument to the serial command. > > > > I think GRUB relies on the BIOS/UEIF to provide drivers and typically > > USB was only > > used to emulated old hardware like keyboard/mouse and CD-ROMs. > > > > Coreboot - is a BIOS/UEIF replacement and so it can do anything they > > care to implement - but then it has to be > > customised for each individual hardware case where as GRUB can rely on > > the standardised routines. > > > > But perhaps things have moved on - it would be great if UEIF provided > > some standard USB drivers for serial. > > Thank you Andrew and Daniel for information and suggestions. Seems You are welcome! > like I have to figure out what drivers are provided with UEIF. Or > simply just get another motherboard with a 8250/16550 compatible > serial port. I think that this is the simplest solution at this point. Anyway, I will try to take a look at this issue when I less busy. Daniel