Date: Fri, 3 Jan 2014 17:59:14 +0000 From: Markus Pfeiffer <markus.pfeiffer@morphism.de> To: Ian Lepore <ian@FreeBSD.org> Cc: freebsd-arm@FreeBSD.org Subject: Re: FreeBSD 10 on Dockstar (Marvell Kirkwood) Message-ID: <20140103175914.GC98342@moore.morphism.de> In-Reply-To: <1388770603.1158.273.camel@revolution.hippie.lan> References: <20131231211054.GA90299@moore.morphism.de> <1388770603.1158.273.camel@revolution.hippie.lan>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] Hi Ian, On Fri, Jan 03, 2014 at 10:36:43AM -0700, Ian Lepore wrote: > On Tue, 2013-12-31 at 21:10 +0000, Markus Pfeiffer wrote: > > Hi all, > > > > I managed "fixing" it by editing the dockstar.dts file and putting for ranges: > > > > ranges = <0x0 0x2f 0xf9300000 0x00100000> > > > > Now I just have to figure out why this "fixes" it, and what damage that patch > > does. > > I also have some pathces for the LED on the dockstar which will tip up in my > > github soon. > > > > Cheers, > > markus > > After looking at the marvell code and docs, and some info I found about > the dockstar at OpenWRT.org, I think the attached patch is the right fix > for a dockstar (it maps the nand flash, and removes mappings for NOR > flash and an LED; the dockstar doesn't seem to have NOR flash, and the > LED thing seems to be out of place). > Can I find information anywhere as to what this ranges command actually means? I was assuming it has something to do with memory mappings, but I didn't find any info as to what in particular the 0x2f _means_. > Markus, could you please test this; if it works, I'll commit it. The > only marvell hardware I have for testing is DreamPlug. It does indeed work. I am a bit surprised that noone seems to be running FreeBSD on a dockstar seriously enough to run into these problems. Some ugly problem in connection with USB seems to rear it's head atm: if I fsck a filesystem, it finds a lot of DUPs and starts deleting perfectly fine files. I changed to using sync as well as disabling clustered reads and writes. Maybe I'll find the time to investigate this issue as well. I hacked a bit on the gpio/led driver to make the LED work with gpioled, I'll post a patch to the mailing list when it's cleaned up if that's ok. markus [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (DragonFly) iQIcBAEBAgAGBQJSxvpyAAoJEBRHBRYBD4mPI+sQAID5vge/l4iD0RuqTALk/m3R zKfoJ2IxCmOrhtm3kYlD4O5yHmTLgg4kXRjo1AxF2oOEH75adM/wvNdTFGgikVUg VolOax0UcT4EpprrQfbqc2soUxALc2wlEvlEGwcFeWpGAG76UF8VT0UTl5LG97uv umrHI5k9emlw/+1ebvydVjrGcVqBbt+wvm3dyLJDJZSYhmMGqAjk5V+ODBhCbIMo gzGwQsOcKqnlF36ibbhU9dzcoAqP9lHg7Hci/WredIwWUUYkYjOdwsTWPMi8Kheq LPSwauIU97DRLBIQ6csO8XF7xqr9xCEPly/9/OpxCb6iGWha/1ocznCkwWgzZlV0 281Ae1lWM6s1ApwCBcTpJhe/jcvrNCICHmXAitp79GY6bJ9n5VKf15Pz9sb3w7U6 tXO7VLMHSQkzb3lYnAAQ4vP4jNZlUpzK63e8IfBFzysF7HyYSojF/UXsSS3Cx95N v3Lmuxls8BOSN7LcthBHP5NksNIQwQxO8S69qYPAu1EagJNmKYmhlcxpfxCeahO7 d7H37/eWxhSHX1P7w5Sw1Gx6rhMQM/M8US54b/AHgLkVL5dvbHVcSNjGS16SrOpk yGoYnt6pQUCONI/Q/HJTuVh+aTXN6PlMNNt1CLg9tZyPqfxQDGEuCqvd2HxK4RJC hDbiI2SnmF18skGqHaOL =uMpn -----END PGP SIGNATURE-----help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140103175914.GC98342>