From: guenter@roeck-us.net (Guenter Roeck)
To: linux-arm-kernel@lists.infradead.org
Subject: ARMADA 370 - Distributed Switch Architecture (dsa) - device tree
Date: Tue, 14 Oct 2014 06:30:29 -0700 [thread overview]
Message-ID: <543D2575.6050209@roeck-us.net> (raw)
In-Reply-To: <60c451c4cbeb4666fff3b45ffdcb780e@twien.net>
On 10/13/2014 11:05 PM, post at twien.net wrote:
> Hi Guenter,
> I'm doing this for my employer and have currently no plans for submitting this upstream. Not that I think we will not be willing to, but it's still very premature and I have so far not been able to test this. Am basically struggling to get 'dsa' up and working.
Hah, yes, that has its own challenges. Took me a while too.
I can send you a working platform file if you think it would help,
though that would be for x86, not for devicetree use.
Also, I could publish a branch with my 6352 driver on top of
the 3.14 kernel (which is where it is currently used) if it helps.
Guenter
> Best,
> Tormod
>
> On 2014-10-13 20:25, Guenter Roeck wrote:
>> On Mon, Oct 13, 2014 at 12:14:41PM +0200, post at twien.net wrote:
>>> Dear all,
>>> I have a custom board equipped with an ARMADA 370 SoC (88f6W11) and
>>> a Marvell switch chip (88e6352) (I have written a device driver for
>>> the latter).
>>
>> Hi Tormod,
>>
>> coincidentially, I have a DSA driver for 88e6352 almost ready for submitting it
>> upstream. What are your plans for your driver ? Do you plan to submit it
>> upstream ? Either case, it would be great if you could share a pointer to it
>> so we can make sure that it works for both our use cases.
>>
>> I have made my patch set available in the 'dsa' branch of
>> https://git.kernel.org/cgit/linux/kernel/git/groeck/linux-staging.git
>> in case you are interested.
>>
>> Thanks,
>> Guenter
>
next prev parent reply other threads:[~2014-10-14 13:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-13 10:14 ARMADA 370 - Distributed Switch Architecture (dsa) - device tree post at twien.net
2014-10-13 11:19 ` Jason Cooper
2014-10-23 9:20 ` Thomas Petazzoni
2014-10-23 12:10 ` Jason Cooper
2014-10-23 12:57 ` post at twien.net
2014-10-23 14:05 ` Andrew Lunn
2014-10-23 14:19 ` post at twien.net
2014-10-13 13:19 ` Andrew Lunn
2014-10-13 18:25 ` Guenter Roeck
2014-10-14 6:05 ` post at twien.net
2014-10-14 13:30 ` Guenter Roeck [this message]
2014-10-14 11:35 ` Richard Cochran
2014-10-14 13:24 ` Guenter Roeck
2014-10-23 8:32 ` Richard Cochran
2014-10-14 2:08 ` Florian Fainelli
2014-10-14 11:14 ` post at twien.net
2014-10-14 16:14 ` Florian Fainelli
2014-10-15 13:42 ` post at twien.net
2014-10-15 13:47 ` Guenter Roeck
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=543D2575.6050209@roeck-us.net \
--to=guenter@roeck-us.net \
--cc=linux-arm-kernel@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 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.