[senz]

Hello,

Can someone answer if Ticket #1039 is fixed?

It was closed 12days ago, dunno if support was added?

http://svn.dd-wrt.com:8000/ticket/1039

Someone might know.

BR

/Dennis

[senz]

Spend 10minutes looking for history and didn't find it, that's why I posted this thread... But as kind as you are, maybe you could post a link?

Thanks!

[senz]

[senz]

But that didn't give me much info more then what was already stated in http://svn.dd-wrt.com:8000/ticket/1039

[epek]

Kodo, which history do you mean?

[ ]: The previous 45 pages of the wrt160nv2 thread
[ ]: The ticket's historic and new comments
[ ]: Other, please link here:.....

Fact is, the driver already exists in WRT160NL which is an atheros architecture.
The rtl8306(s) driver is delivered with openwrt bleeding edge and is present in stable variants too.
The only thing missing seems to be that someone compiles ramips rt28xx-platform codebase with the switch driver linked to it. I am not developer enough to tell by expericence. I guess sash has already debugged previous build with serial or jtag, so his assumptions that only the switch is not working are correct.

I would be pleased push the wrt160nv2 project over the target line, if I knew for sure how to either integrate the driver myself into dd-wrt or openwrt, or if anyone could tell me how to identify the lines of an old nokia clone cable correctly in order to resemble a level shifter serial port.

If you know of a manual for either or both of them, let me know.
Building a device profile seems to be different here.

Thanks for your advise!
Regards
epek

[epek]

Kodo, thanks for your reply.

The last relevant things that happened were, chronologically:

--------------------------
Changed 3 years ago by Chrisbert

Owner changed from Chrisbert to Brainslayer

comment:8 Changed 17 months ago by Sash

Resolution set to fixed
Status changed from new to closed

comment:9 Changed 17 months ago by Sash

Resolution fixed deleted
Status changed from closed to reopened

as LOM mentioned Felix wrote a working driver.
​https://dev.openwrt.org/browser/trunk/target/linux/generic/files/drivers/net/phy/rtl8306.c
comment:10 Changed 17 months ago by Sash

..which is already used in the wrt160NL
comment:11 Changed 2 weeks ago by Sash

Resolution set to fixed
Status changed from reopened to closed
-------------------------------------------


So as far as I understand it, Sash knows about the driver used in WRT160N/L/ (which is atheros) and set the ticket for WRT160N v2 (which is ramips) to fixed/closed.

So this either says that the rt2880 SoC plattform code received an update to correctly address the rtl8306sd code. As a result a working build is now within reach

The other interpretation would be: Sash mixed up the two devices - which I do not suppose would happen to him.

Browsing the source does indicate recent changes made by brainslayer within the rt2880(f) subtree.
Unfortunately was was unable to recognize neither patterns containing 8306 there nor to find a device config within
http://svn.dd-wrt.com:8000/browser/src/linux/rt2880/linux-2.6.23/

This may be very well caused by my impatientience to read all of the tree's code as well as my incompetence to
identify a device specific adaption for a WRT160N v2.

..which leads back to senz's question dated Jan, 5th 2012...

So, if you have any information for me on what you can read there, which I can't - or whatever different information - your are most welcome to share it with us.


Thanks for your efforts!

[epek]

Thanks for your reply, kodo!

Do you think it is a very efficient way to keep reopening tickets before all the necessary facts are accessible - or just because they lack conclusive information?

Discussion is the purpose of a forum, isn't it?

IMO using the ticketing system for this in avoidable matters would be rather spammy, don't you agree?

[epek]

@kodo Btw: "Changelog: http://http://svn.dd-wrt.com/timeline" should read "Changelog: http://svn.dd-wrt.com:8000/timeline"