Hi, > Does this mean that we have abandoned the dscape code? No. I think we > need the capabilities provided by the dscape code as well. I just don't > think we can make progress as quickly with the dscape code as we can > this way. > > So what happens to dscape? I will publish a wireless-dev tree that > will start life as a copy of the current dscape branch. This will > provide a home for dscape-related development while allowing us more > freedom to break things. Once we get things where we want them in > wireless-dev, we can move pieces back to wireless-2.6.
I may have missed an announcement on this, but has the wireless-dev tree containing the recent dscape stack + drivers already been published? It seems the dscape stack including the drivers for it have been removed from the wireless-2.6 git tree, and I am wondering where I can pull the most recent version of the dscape stack now. IvD
pgpQxYR9bLXAg.pgp
Description: PGP signature
