wandboard / imx6 / exynos4 / cortex-a9 "wrong-endian bug" fixed

[Ian Lepore]

On Tue, 2014-02-11 at 14:44 +0100, Bernd Walter wrote:
> On Tue, Feb 11, 2014 at 02:07:33AM +0100, Bernd Walter wrote:
> > On Mon, Feb 10, 2014 at 07:33:52AM -0700, Ian Lepore wrote:
> > > On Mon, 2014-02-10 at 05:13 +0100, Bernd Walter wrote:
> > > > On Mon, Feb 03, 2014 at 12:04:50AM +0100, Bernd Walter wrote:
> > > [...]
> > > > Second boot worked better, but booting hanged after devd.
> > > > ...
> > > 
> > > I have also seen this hang in devd during rc-script processing, a few
> > > times recently.  ^T always shows it to be in a nanslp wait.
> > 
> > Never seen this again so far.
> > 
> > > I've never used crochet or tried to use growfs, that may not be an
> > > arm-related problem from the looks of it.
> > 
> > Someone said he hadn't seen it on a recently updated Beaglebone, but
> > not sure how recent the source code had been.
> > I can't do Beaglebone tests myself, since I'm waiting for new boards.
> > 
> > > I've never had getty/login hang in nanslp like that.  When I'm running
> > > with nfs root it tends to hang in rpccon state, and that's frequency and
> > > annoying enough that I'm going to have to debug it soon (for all I know
> > > that problem may be my old 8.4 nfs server).
> > 
> > Interesting.
> > 
> > I can't seen to get the second microSD-slot running.
> > The controllers get attached, but mmc only to the onboard slot.
> > The WiFi is SDIO, which I didn't compile into the kernel and I noticed
> > there is a GPIO used to enable the chip.
> 
> Strange enough the 4th controller gets an mmc1 device attached:
> sdhci_imx3: <Freescale uSDHC controller> mem 0x219c000-0x219ffff irq 57 on simplebus2
> sdhci_imx3-slot0: 200MHz HS 4bits 3.3V 3.0V PIO
> sdhci_imx3-slot0: ============== REGISTER DUMP ==============
> sdhci_imx3-slot0: Sys addr: 0x00000000 | Version:  0x00000002
> sdhci_imx3-slot0: Blk size: 0x00000000 | Blk cnt:  0x00000001
> sdhci_imx3-slot0: Argument: 0x00000000 | Trn mode: 0x00000000
> sdhci_imx3-slot0: Present:  0xf78d8088 | Host ctl: 0x00000000
> sdhci_imx3-slot0: Power:    0x0000000d | Blk gap:  0x00000080
> sdhci_imx3-slot0: Wake-up:  0x00000008 | Clock:    0x00000002
> sdhci_imx3-slot0: Timeout:  0x00000080 | Int stat: 0x00000000
> sdhci_imx3-slot0: Int enab: 0x017f00fb | Sig enab: 0x017f00fb
> sdhci_imx3-slot0: AC12 err: 0x00000000 | Slot int: 0x00000000
> sdhci_imx3-slot0: Caps:     0x0377c800 | Max curr: 0x80000000
> sdhci_imx3-slot0: ===========================================
> mmc1: <MMC/SD bus> on sdhci_imx3
> 
> It hangs on probing, but it is my understanding that this controller
> isn't wired at all on wandboard.
> But why isn't there an attachment with the other two controllers.
> 

I can't get the uSD slot on the carrier board to work either, but my
symptoms are different.

Aha!  I just noticed that Freescale moved some bits around in the
Present State register and defined some that are undefined in the spec
and so on.  I completely overlooked that when I was writing the
driver.  

I need to write some proper translation routines, which ain't happening
tonight. :)  But, as proof of concept, the attached little crude hack
makes it successfully probe both of my sd slots now.

-- Ian

-------------- next part --------------
A non-text attachment was scrubbed...
Name: imx_sdhci_detect_hack.diff
Type: text/x-patch
Size: 445 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-arm/attachments/20140211/3f8991e3/attachment.bin>