Hi Experts,
Is there any development on XHCI support on GRUB2? New Intel boards (e.g.
Apollo Lake) has only XHCI controller so none my USB device (keyboarrd,
mass storage) works on GRUB2 on this board.
If there is any work going on, I can help with testing/development but
don't know where to star
Hi Experts,
I am using GRUB2 on intel apollo lake board. This board does not have IO
mapped uart instead it has 8250 memory mapped UART.
GRUB2 does not recognize memory mapped uart and gives error ("serial port
COM0 not found). There is a 8250 memory mapped driver available in
coreboot. Is it pos
g/archive/html/grub-devel/2017-02/msg00104.html
> >
> >
> > On Wed, Mar 1, 2017 at 9:15 AM, Gailu Singh wrote:
> >> Hi Experts,
> >>
> >> I am using GRUB2 on intel apollo lake board. This board does not have IO
> >> mapped uart instead it has
Sorry for typo. I meant 8250 instead of 8050 in last email
On Wed, Mar 1, 2017 at 3:21 PM, Gailu Singh wrote:
> My board is Intel Oxbohill CRB (Apollo lake). On my board UART are not
> connected to PCI.
>
> I am using grub2 payload loaded by coreboot. UART works fine in coreboo
follows
cat syminfo.lst | sort | gawk -f ./genmoddep.awk > moddep.lst || (rm -f
moddep.lst; exit 1)
grub_ns8250_pci_mmio_init in serial is not defined
make[3]: *** [moddep.lst] Error 1
On Wed, Mar 1, 2017 at 3:27 PM, Gailu Singh wrote:
> Sorry for typo. I mean
llowed in C99 mode)
I will check PCI vendor ID and Device ID and get back to you.
On Wed, Mar 1, 2017 at 4:27 PM, Matthias Lange <
matthias.la...@kernkonzept.com> wrote:
> On 03/01/2017 11:32 AM, Gailu Singh wrote:
> > I checked coreboot where in the memory it is mapped and
Hi Experts,
I am using GRUB2 on intel apollo lake board. This board does not have IO
mapped uart instead it has 8250 memory mapped UART.
GRUB2 does not recognize memory mapped uart and gives error ("serial port
COM0 not found). There is a 8250 memory mapped driver available in
coreboot. Is it pos
Hi Experts,
Is there any development on XHCI support on GRUB2? New Intel boards (e.g.
Apollo Lake) has only XHCI controller so none my USB device (keyboarrd,
mass storage) works on GRUB2 on this board.
If there is any work going on, I can help with testing/development but
don't know where to star
Thanks for the update. I will try your patches on Apollo lake and report
back the results. Intel strategy seems to be XHCI only option on newer
boards so sooner or later xhci support is required in Grub. Thanks for your
effort to take initiative.
On Wed, Mar 1, 2017 at 4:07 PM, Bjørn Forsman
wrot
9:29 AM, Andrei Borzenkov
wrote:
> 02.03.2017 06:00, Gailu Singh пишет:
> > Thanks for the update. I will try your patches on Apollo lake and report
> > back the results. Intel strategy seems to be XHCI only option on newer
> > boards so sooner or later xhci support is req
ion sufficient to find the required information?
On Wed, Mar 1, 2017 at 4:34 PM, Gailu Singh wrote:
> Build problem was due to not running ./configure. I only did make clean
> and make. Build issue is now resolved after running configure. Only
> cosmetic change in your patch.
>
>
Getting Build error related to include path. Looks like some Makefile
problem
bus/usb/xhci/usb/xhci.c:36:26: fatal error: arch/virtual.h: No such file or
directory
#include
On Thu, Mar 2, 2017 at 9:42 AM, Gailu Singh wrote:
> I am not using EFI. I am using coreboot with Intel FSP. In
grub.elf but there is no sign
of life on USB keyboard that is connected to USB3.0 on Intel Oxbohill CRB
(Apollolake SOC).
Thanks.
On Sun, Mar 5, 2017 at 8:55 PM, Bjørn Forsman
wrote:
> On 5 March 2017 at 16:11, Gailu Singh wrote:
> > Getting Build error related to include path. Looks
:~#
On Mon, Mar 6, 2017 at 3:13 PM, Bjørn Forsman
wrote:
> On 5 March 2017 at 18:22, Gailu Singh wrote:
> > git clone https://github.com/bjornfor/grub/
> > git checkout add-coreboot-xhci-driver-2nd-attempt-v2
> > ./autogen.sh
> > ./configure --with
Hi Experts,
I am using grub2 with coreboot and configured with --with-platform=coreboot.
I am able to load grub2 from coreboot. However when I run ls command, I do
not see cbfsdisk. ls only shows
(memdisk) (ahci0) (ahci0,msdos1) (ahci0,msdos2)
I have added file in the cbfs as follows and need
b.cfg=./coreboot.cfg
This must be something else. AFAIK memdisk itself resides in CBFS,
Strangely ls comman shows memdisk but not cbfsdisk
On Fri, Mar 17, 2017 at 12:52 AM, Vladimir 'phcoder' Serbinenko <
phco...@gmail.com> wrote:
>
>
> On Thu, Mar 16, 2017, 12:18 Gailu
>>What address it prints?
I followed suggested steps and I see following print
fs/cbfs.c:347: head=0x
On Fri, Mar 17, 2017 at 8:57 AM, Andrei Borzenkov
wrote:
> 16.03.2017 22:43, Gailu Singh пишет:
> >>> Try insmod cbfs
> >
> >>
> > Tri
il.com> wrote:
>
>
> On Thu, Mar 16, 2017, 22:30 Gailu Singh wrote:
>
>> Please find coreboot image attached. Zipped it to reduce size
>>
> This image is actually fine and is read correctly by fstest. Apparently
> for some reason reading image at the end of 4GiB doesn
>>Any chance ROM is mapped somewhere else in your case?
I need to check, this may be a case.
On Fri, Mar 17, 2017 at 7:16 PM, Andrei Borzenkov
wrote:
> On Fri, Mar 17, 2017 at 4:24 PM, Gailu Singh wrote:
> > @Vladimir
> > I do not have serial console (board has memory ma
Hi Experts,
We are using coreboot + grub to load Linux. We display splash screen in
coreboot but this splash screen is wiped out by GRUB. Our requirement is to
continue same splash screen (loaded by coreboot) on display until Linux
booting is completed. Grub console/menu is needed on on serial por
Mar 20, 2017 at 4:06 PM, Daniel Kiper wrote:
> On Mon, Mar 20, 2017 at 02:58:01PM +0530, Gailu Singh wrote:
> > Hi Experts,
> >
> > We are using coreboot + grub to load Linux. We display splash screen in
> > coreboot but this splash screen is wiped out by GRUB. Our requ
It was indeed the ROM mapping issue. solved now. Thank you so much Andrei.
On Fri, Mar 17, 2017 at 7:29 PM, Gailu Singh wrote:
> >>Any chance ROM is mapped somewhere else in your case?
> I need to check, this may be a case.
>
> On Fri, Mar 17, 2017 at 7:16 PM, Andrei Borzenkov
, Mar 3, 2017 at 7:11 PM, Matthias Lange <
matthias.la...@kernkonzept.com> wrote:
> Hi,
>
> On 03/03/2017 01:03 PM, Gailu Singh wrote:
> > Sorry it took some time to boot board with Linux. Not sure how to
> > determine correct Device ID, Vendor ID seems to be all 8086
Adrian
https://www.coreboot.org/pipermail/coreboot/2017-March/083681.html
On Fri, Mar 24, 2017 at 10:49 PM, Vladimir 'phcoder' Serbinenko <
phco...@gmail.com> wrote:
>
>
> On Fri, Mar 24, 2017, 10:17 Gailu Singh wrote:
>
>> It was indeed the ROM mapping iss
:32, Gailu Singh пишет:
> >>> Could you please reference the solution for future users with the same
> > problem?
> > Sure. Infect I should have detailed it without asking. Sorry for that.
> >
> > Solution can be referenced to following thread in coreboot mailing
ov wrote:
>
>> 25.03.2017 10:22, Vladimir 'phcoder' Serbinenko пишет:
>> > On Sat, Mar 25, 2017, 00:16 Andrei Borzenkov
>> wrote:
>> >
>> >> 24.03.2017 21:38, Gailu Singh пишет:
>> >>> This is how it is calculated in coreboot
>
24, 2017 at 10:59 PM, Gailu Singh wrote:
> Hi Matthias,
>
> The patches I send to the mailing list do not support the Intel UARTs
> right now, because they only match for OXSemi IDs. One has to add a
> similar matching block to 'ns8250_pci_mmio_iter' for the I
grub menu if I specify (usb1) next time menu does not work automatically
and I need to edit it on nearly every power cycle, occasionally it is
listed with same name as in last power cycle.
Thank you once again for taking initiative on this feature.
On Mon, Mar 6, 2017 at 3:28 PM, Gailu Singh
Hi Experts,
When I try to configure CBFS_SIZE and ROM_SIZE to be same in coreboot, grub
fails to detect CBFS file system. If I keep min 64KB difference between
ROM_SIZE and CBFS_SIZE then it works fine.
Can someone please explain why can't I have ROM_SIZE and CBFS_SIZE to be
same.
Below are the
isk, 0, header_off,
sizeof (head), &head))
{
grub_dprintf ("cbfs", "FAIL:: :%s:%d\n",__FILE__,__LINE__);
goto fail;
}
Does this gives any idea what could be the problem when CONFIG_CBFS_SIZE
and CONFIG_ROM_SIZE is same in coreboot configuration?
On Thu,
30 matches
Mail list logo