From: Bjorn Helgaas <helgaas@kernel.org>
To: Carlo Pisani <carlojpisani@gmail.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: Oxford Semiconductor Ltd OX16PCI954 - weird dmesg
Date: Mon, 4 Nov 2019 09:58:22 -0600 [thread overview]
Message-ID: <20191104155822.GA106911@google.com> (raw)
In-Reply-To: <CA+QBN9AzXHifP4=F1O1jjbGP0yNxBZeTPgPJvpcKFb9Z4f30KA@mail.gmail.com>
[+cc linux-pci (please keep the list copied so others can
contribute/benefit and it's searchable via list archives)]
On Mon, Nov 04, 2019 at 04:25:02PM +0100, Carlo Pisani wrote:
> > I think the first step is to fix the problem that prevents current
> > kernels from booting. It's not really practical to debug v4.4.
>
> does anyone have a modern kernel working for rb532?
> because I suspect Linux is in regressing regarding this point.
I have no idea what rb532 is or whether Linux is regressing on it.
Any platform that isn't tested occasionally does tend to regress over
time.
> > It sounds like the firmware fails to even load v4.11? If that's the
> > case, it's probably not a problem with the kernel itself, since it
> > hasn't even started executing. Possibly a kernel size problem? Maybe
> > the v4.11 kernel is larger than v4.4, v4.9, etc? Does v4.11 boot if
> > you strip out non-essential drivers?
>
> I do not know, and I don't understand. The rb532 manual doesn't say a
> word regarding the maximal size of the kernel, which in our case is
> less than 8Mbyte
Is the v4.11 kernel image bigger than the v4.4 kernel that boots?
> We tried to strip extra functions out of the kernel v5.*, but no dice
>
> hence, first we need to fix kernel 4.4 which boots and work, then we
> can try to understand what is wrong with kernel v5.*
>
> our time is limited, and we have to complete a project rather than
> play with the kernel
Sorry, I should have been more clear. I don't think it's practical
*for me* to debug something on v4.4. It may well be practical for you
because you have different constraints than I do.
Bjorn
next parent reply other threads:[~2019-11-04 15:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+QBN9AzXHifP4=F1O1jjbGP0yNxBZeTPgPJvpcKFb9Z4f30KA@mail.gmail.com>
2019-11-04 15:58 ` Bjorn Helgaas [this message]
[not found] <CA+QBN9D4bckEZmNhLJPBmr92St1W2GGyazLGR9kANFk2cfV8Pg@mail.gmail.com>
2019-11-04 16:30 ` Oxford Semiconductor Ltd OX16PCI954 - weird dmesg Bjorn Helgaas
[not found] <CA+QBN9B4qfxpEa69TB=+MngG9bN0puwByAeGCMxk_Y7fgaKhpQ@mail.gmail.com>
2019-11-04 16:07 ` Bjorn Helgaas
[not found] <CA+QBN9C_o8HanAzXpDUN410g2o5+xfx64pbX3_VHVDKcj5N3kA@mail.gmail.com>
2019-10-28 17:13 ` Bjorn Helgaas
2019-10-28 16:37 ` Carlo Pisani
2019-10-28 18:48 ` Bjorn Helgaas
2019-10-28 18:06 ` Carlo Pisani
2019-10-28 19:43 ` Bjorn Helgaas
2019-10-28 18:49 ` Carlo Pisani
2019-11-04 14:59 ` Bjorn Helgaas
2019-10-28 16:46 ` Carlo Pisani
2019-10-24 17:11 [PATCH v6 00/30] PCI: Allow BAR movement during hotplug Sergey Miroshnichenko
2019-10-24 17:11 ` [PATCH v6 01/30] PCI: Fix race condition in pci_enable/disable_device() Sergey Miroshnichenko
2019-10-25 14:33 ` Oxford Semiconductor Ltd OX16PCI954 - weird dmesg Carlo Pisani
2019-10-25 16:37 ` Bjorn Helgaas
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=20191104155822.GA106911@google.com \
--to=helgaas@kernel.org \
--cc=carlojpisani@gmail.com \
--cc=linux-pci@vger.kernel.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.