Hi Jonathan, On Friday 09 November 2012 06:11:47 Jonathan Bither wrote: > Good morning list, > I was writing to ask if there is a current maintainer for the Atheros > target that I may contact. > The reason that I ask is because I was contacted about a patch that I had > submitted prior in regards to allowing various EnGenius devices to > successfully reboot without a kernel hang. The patch didn't receive feedback > and was never accepted. > > I know that most maintainers have moved on to more common and higher > performance chipsets as of late, however there are still a lot of ar231x and > ar531x chipsets still in the field. > > I will be required to maintain updates on these chipsets for my company and > as such I would like to find the best way to submit various patches to the > target with the highest probability of getting accepted. Would me cloning the > OpenWRT mirror on github and submitting pull requests be sufficient, or would > each patch source have to be sent through the mailing list? > > Currently the target is setup through patch sets. I know that this was > intended so that the platform could ultimately be mainlined into the kernel > easily. I ask if I may break apart the patch sets into the 'files-3.x' > overlay layout temporarily as other targets have, so that I may be able to > submit various patches in a more timely manner as opposed to patching patch > sets. These could just as easily be transferred into patch form again in the > event of a push to get the target mainlined. > > On my TODO: > Remove duplicate code between the ar231x and ar531x platforms. > Address all gpio/led polling flash errors. > Determine the hardware limitation of the CPU processing/Ethernet speed. > Add ethtool support to the Ethernet driver. > Add BQL to the Ethernet driver. > Rewrite sections of the Ethernet driver for maximum performance. > Add gpio detection mechanisms to address EnGenius products cleanly. > > Any feedback is greatly appreciated.
As others said, please go ahead and send your patches to the mailing-list. I still have an AR2318-based device I could use for testing. One thing that you might want to add is also: - reading the initial UART baudrate setting and use that instead of hardcoding it to 9600 (the board mentionned above uses 115200) Thank you! -- Florian _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
