Hi,
I'm trying to get started with the new i.MX8MQ-EVK support and I've
got a bit of an issue enabling ext4 read support without also enabling
write support.
CONFIG_FS_EXT4=y
I get a build error here:
fs/fs.c:198:12: error: ‘ext4_write_file’ undeclared here (not in a
function); did you mean ‘ex
Hi Fabio,
> Does the change below help?
Your patch does indeed fix the problem.
Thanks,
Chris
___
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
On Thu, 3 Jan 2019 at 12:53, Chris Spencer wrote:
> Hi,
>
> I'm trying to get the i.MX8MQ-EVK board up and running with the
> recently added kernel support (I'm currently working off
> arm-soc/for-next) and am having some trouble with the networking. If I
> issue a pi
On Fri, 4 Jan 2019 at 15:33, Chris Spencer wrote:
>
> On Thu, 3 Jan 2019 at 12:53, Chris Spencer wrote:
> > Hi,
> >
> > I'm trying to get the i.MX8MQ-EVK board up and running with the
> > recently added kernel support (I'm currently working off
> >
[CC'd the list this time..]
On Wed, 9 Jan 2019 at 13:56, Stefano Babic wrote:
> Sorry, I was on holidays and afterwards I have to resume some work in
> office ;-)
>
> I am now looking for which patches should be merged in release and I
> will pick them up.
Hi Stefano,
If I may make my own (self
Stefano,
On Wed, 9 Jan 2019 at 15:14, Stefano Babic wrote:
> > https://patchwork.ozlabs.org/patch/1019908/
>
> I have seen this patch to solve "bashism", I confess I had to think
> about what is it. "=" instead of "==" is quite unnatural for me, but
> yes, first thing I do on a new installed syst
On Thu, 31 Jan 2019 at 18:43, Sergey Kubushyn wrote:
> OK, it worked. The second patch is irrelevant for me because I'm working on
> a custom device, not MCIMX8M-EVK (I don't have that, just using its
> schematic from time to time as reference to its drivers and such) and I
> _DID_ have "CONFIG_PI
On Fri, 1 Feb 2019 at 16:10, Sergey Kubushyn wrote:
> > Turns out there's already a patch to add the driver as part of the
> > i.MX8MM patch series. [1] Go figure.
>
> What the fcuk is i.MX8MM? Are they going to do anything with their i.MX8MQ
> documentation? It is currently at Rev.0 dated January
esync with savedefconfig")
Signed-off-by: Chris Spencer
---
Depends on this patch: https://patchwork.ozlabs.org/patch/1031817/
---
configs/imx8mq_evk_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/configs/imx8mq_evk_defconfig b/configs/imx8mq_evk_defconfig
index 53025e45bc..
From: Chris Spencer
The Ethernet controller is not able to initialise correctly without the
pinctrl driver.
This config setting was enabled in the initial version of this file,
but was removed by a savedefconfig resync because the parameter did not
actually exist at that point.
Fixes
On Thu, 28 Feb 2019 at 12:58, Fabio Estevam wrote:
> Hi,
>
> I am not able to build top of tree U-Boot for imx8mq-evk:
>
> WARNING './spl/u-boot-spl-ddr.bin' not found, resulting binary is
> not-functional
> make[1]: Nothing to be done for 'SPL'.
> CFGCHK u-boot.cfg
>
> It works fine when I bu
On Fri, 1 Mar 2019 at 01:49, Peng Fan wrote:
> > Hi Peng,
> >
> > On Thu, Feb 28, 2019 at 10:17 PM Peng Fan wrote:
> > >
> > > Did you execute `make flash.bin`?
> >
> > Yes, I did, but flash.bin is not generated for me in mainline U-Boot tree,
> > only in
> > u-boot-imx tree.
>
> That's weird, I
On Mon, 4 Feb 2019 at 10:05, Chris Spencer wrote:
> From: Chris Spencer
>
> The Ethernet controller is not able to initialise correctly without the
> pinctrl driver.
>
> This config setting was enabled in the initial version of this file,
> but was removed by a savedefconf
On Sat, 2 Mar 2019 at 06:27, Peng Fan wrote:
> > On Mon, 4 Feb 2019 at 10:05, Chris Spencer wrote:
> > > From: Chris Spencer
> > >
> > > The Ethernet controller is not able to initialise correctly without
> > > the pinctrl driver.
> > >
&
On Thu, 24 Jan 2019 at 23:51, Sergey Kubushyn wrote:
> On Fri, 4 Jan 2019, Chris Spencer wrote:
> Hi Chris,
>
> Did you figure out what was wrong with the PHY always reading zeroes over
> MDIO?
>
> I have exactly same problem here with out i.MX8MQ-based device -- it worked
&
On Sat, 26 Jan 2019 at 01:14, Sergey Kubushyn wrote:
> Thanks for a reply. The problem here is not with leftover descriptors -- it
> is MDIO bus not working at all. It is either bogus speed/clock in DM mode or
> something else that I haven't found yet. Reading all zeroes means there is
> no commun
e it intermittently uses
the wrong phy driver, but, with this change, the generic phy driver
now seems to work fine. I guess maybe U-Boot is now leaving the phy in
a different state that happens to work.
Chris
From 5af35b93185541245b7d77fd8e73e616c4219086 Mon Sep 17 00:00:00 2001
From: Chris
17 matches
Mail list logo
