From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v2] i2c: add Marvell 64xxx driver
Date: Tue, 22 Jul 2014 18:53:52 +0200 [thread overview]
Message-ID: <53CE9720.6050204@gmail.com> (raw)
In-Reply-To: <20140722202150.923eb98d9268383756226e99@gmail.com>
On 07/22/2014 06:21 PM, Antony Pavlov wrote:
> On Tue, 22 Jul 2014 10:51:10 +0200
> Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com> wrote:
>> I finally finished work on xHCI and PCI on Armada 370. Now I come
>
> Are you speaking about PCIe support for Armada 370 in barebox?
Yes, but not only on Armada 370 but Orion SoCs in general. I am about
to clean the PCIe driver now and see if I can give it a go on Dove or
Kirkwood easily.
This is what I got today with both PCIe driver and xHCI PCI driver:
barebox 2014.07.0-00181-g2d9d176ef3c7-dirty #1081 Tue Jul 22 09:20:08
CEST 2014
Board: Globalscale Mirabox
xHCI PCI pci0: USB xHCI 0.96
barebox:/ usb
USB: scanning bus for devices...
Using index 0 for the new disk
Bus 001 Device 002: ID 0951:1653 DT 100 G2
Bus 001 Device 001: ID 0000:0000 USB 3.0 Root Hub
2 USB Device(s) found
barebox:/ mount -a
ext4 ext40: EXT2 rev 1, inode_size 256
none on / type ramfs
none on /dev type devfs
/dev/disk0.0 on /mnt/disk0.0 type ext4
barebox:/ ls /mnt/disk0.0/
. .. lost+found
Sebastian
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2014-07-22 16:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 21:25 Antony Pavlov
2014-07-16 21:25 ` Antony Pavlov
2014-07-17 9:33 ` Sebastian Hesselbarth
2014-07-17 11:59 ` Antony Pavlov
2014-07-22 8:51 ` Sebastian Hesselbarth
2014-07-22 9:57 ` Antony Pavlov
2014-07-22 11:05 ` Sebastian Hesselbarth
2014-07-22 11:58 ` Antony Pavlov
2014-07-22 16:21 ` Antony Pavlov
2014-07-22 16:53 ` Sebastian Hesselbarth [this message]
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=53CE9720.6050204@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox