[rfc] moving sys/mips/atheros to sys/mips/ar71xx, and moving sys/mips/atheros/ar531x to sys/mips/ar531x

[Adrian Chadd]

hiya,

The atheros MIPS stuff is a little badly organised. I'd like to
reorganise it a little:

* sys/mips/atheros - is the only shared bits (ie, the bus space code)
* sys/mips/ar71xx - atheros 71xx and later
* sys/mips/ar531x - the earlier generation mips4kc cores

It'll require a bit of svn mv'ing things around and will likely upset
anyone with branches, but I'd rather do this shuffling before
12.0-RELEASE is cut.

Any objections?



-adrian

[Aleksandr Rybalko]

Hi Adrian,

maybe better to move inside sys/mips/atheros?
sys/mips/atheros/common
sys/mips/atheros/ar71xx
sys/mips/atheros/ar531x

Thanks!

Post by Adrian Chadd
hiya,
The atheros MIPS stuff is a little badly organised. I'd like to
* sys/mips/atheros - is the only shared bits (ie, the bus space code)
* sys/mips/ar71xx - atheros 71xx and later
* sys/mips/ar531x - the earlier generation mips4kc cores
It'll require a bit of svn mv'ing things around and will likely upset
anyone with branches, but I'd rather do this shuffling before
12.0-RELEASE is cut.
Any objections?
-adrian
_______________________________________________
https://lists.freebsd.org/mailman/listinfo/freebsd-arch

[Adrian Chadd]

Post by Aleksandr Rybalko
Hi Adrian,
maybe better to move inside sys/mips/atheros?
sys/mips/atheros/common
sys/mips/atheros/ar71xx
sys/mips/atheros/ar531x

I don't mind doing that, it's just a lot of nested directories. :-)

What do people think of the above? I can do that and then use it as an
excuse to write / tidy up some of the hardware support for other
features that only show up on ar934x and later chips (like an SRAM
driver..)




-adrian

[Warner Losh]

Post by Adrian Chadd

Post by Aleksandr Rybalko
Hi Adrian,
maybe better to move inside sys/mips/atheros?
sys/mips/atheros/common
sys/mips/atheros/ar71xx
sys/mips/atheros/ar531x

I don't mind doing that, it's just a lot of nested directories. :-)
What do people think of the above? I can do that and then use it as an
excuse to write / tidy up some of the hardware support for other
features that only show up on ar934x and later chips (like an SRAM
driver..)

It's what we're doing with all the other vendors that have multiple
directories on both arm and mips. I think it's the right thing to do. It's
been the agreed to convention for at least a decade. While there may be
some minor variance across all the platforms we support, it's the expected
convention...

Warner

[Adrian Chadd]

Post by Warner Losh

Post by Adrian Chadd

Post by Aleksandr Rybalko
Hi Adrian,
maybe better to move inside sys/mips/atheros?
sys/mips/atheros/common
sys/mips/atheros/ar71xx
sys/mips/atheros/ar531x

I don't mind doing that, it's just a lot of nested directories. :-)
What do people think of the above? I can do that and then use it as an
excuse to write / tidy up some of the hardware support for other
features that only show up on ar934x and later chips (like an SRAM
driver..)

It's what we're doing with all the other vendors that have multiple
directories on both arm and mips. I think it's the right thing to do. It's
been the agreed to convention for at least a decade. While there may be some
minor variance across all the platforms we support, it's the expected
convention...

Sweet. I'll do this then.



-adrian