Re: [CFR]RT305xF support, w/o attachment
I urge you to have a closer look at ral(4) and it's way of handling
RT2500 and RT2600 specific differences. In it's simplest form you can
copy the OpenBSD code 1:1 without any functional changes, heck, it's
the source of this driver anyway.
--
Bernhard
I've look on difference between RT2[56]00 and RT2860 some time ago, but done
it again, and found that we can only place
RT2860/RT3090 support under same name (ral), but hardware have too big
difference. And in case I do this patch for RT3052F SoC,
when I placing RT2860 into ral, i get completely different driver (because
SoC
don't use PCI interface).
So can You (or someone else) hint me, how to done this?
switch (what to do) {
case 'Remake run to support PCI and SoC interface':
Much work to make driver bus independent;
case 'Port OpenBSD one':
driver do not support SoC (SoC device don't have MCU);
break;
case 'Place my RT2860 under dev/ral':
different device in same driver;
break;
}
I'd say porting OpenBSD's is smarter move than remaking run(4).
OpenBSD's ral(4) supports RT2800/RT3090,
http://www.openbsd.org/cgi-bin/man.cgi?apropos=0sektion=4query=ralmanpath=OpenBSD+Currentarch=i386format=html
so ported code should nicely fit into FreeBSD's sys/dev/ral/ folder.
It seems pci related code is separated,
http://fxr.watson.org/fxr/source/dev/ral/
driver - pci code might nicely fit SoC code too.
FreeBSD's if_runreg.h is the same as OpenBSD's if_rt2860reg.h. (Though, I have
been ignoring syncing changes related to RT3090. run(4) doesn't supports it.)
In
fact, OpenBSD doesn't have if_runreg.h, instead they share if_rt2860reg.h. We
can separate, but 90% of them would be identical.
I don't have h/w but I might be able help you out non-SoC portion of code.
AK
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFR]RT305xF support, w/o attachment
On 22/03/11 01:35 AM, PseudoCylon wrote: FreeBSD's if_runreg.h is the same as OpenBSD's if_rt2860reg.h. (Though, I have been ignoring syncing changes related to RT3090. run(4) doesn't supports it.) In fact, OpenBSD doesn't have if_runreg.h, instead they share if_rt2860reg.h. We can separate, but 90% of them would be identical. I don't have h/w but I might be able help you out non-SoC portion of code. AK I have no objections in Aleksandr's work to port ral(4) from OpenBSD to FreeBSD unless it requires a hardware firmware module as in run(4), and unless there's a way to skip compiling hardware-assisted modules in FreeBSD using the WITHOUT_FIRMWARE option. Likewise, a WITHOUT_OFDM patch for FreeBSD could be ported nicely to OpenBSD... :) Etienne -- Etienne Robillard Company: Green Tea Hackers Club Occupation: Software Developer (and CEO) E-mail: e...@gthcfoundation.org Work phone: 450-936-2123 Website (Company): https://gthc.org/ Website (Blog): https://gthc.org/blog/ PGP public key fingerprint:F2A9 32EA 8E7C 460F 1728 A1A7 649C 7F17 A086 DDEC During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell If a free society cannot help the many who are poor, it cannot save the few who are rich. -- John F. Kennedy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFR]RT305xF support, w/o attachment
as far my knowledge goes, radiation from multi-frequency subcarriers in a multi-path system such as a wireless network (802.11 a/g/n) or a microwave oven is something you definitely want to avoid sitting in while hacking FreeBSD... https://gthc.org/wiki/Advisories/OFDM_20110315 I may have done technical errors but i do not drink in the morning!! :) On 22/03/11 06:30 AM, Adrian Chadd wrote: So I'm curious - what exactly about OFDM do you have a problem with? Adrian On 22 March 2011 18:23, Etienne Robillard e...@gthcfoundation.org mailto:e...@gthcfoundation.org wrote: On 22/03/11 01:35 AM, PseudoCylon wrote: FreeBSD's if_runreg.h is the same as OpenBSD's if_rt2860reg.h. (Though, I have been ignoring syncing changes related to RT3090. run(4) doesn't supports it.) In fact, OpenBSD doesn't have if_runreg.h, instead they share if_rt2860reg.h. We can separate, but 90% of them would be identical. I don't have h/w but I might be able help you out non-SoC portion of code. AK I have no objections in Aleksandr's work to port ral(4) from OpenBSD to FreeBSD unless it requires a hardware firmware module as in run(4), and unless there's a way to skip compiling hardware-assisted modules in FreeBSD using the WITHOUT_FIRMWARE option. Likewise, a WITHOUT_OFDM patch for FreeBSD could be ported nicely to OpenBSD... :) Etienne -- Etienne Robillard Company: Green Tea Hackers Club Occupation: Software Developer (and CEO) E-mail: e...@gthcfoundation.org mailto:e...@gthcfoundation.org Work phone: 450-936-2123 Website (Company): https://gthc.org/ Website (Blog): https://gthc.org/blog/ PGP public key fingerprint:F2A9 32EA 8E7C 460F 1728 A1A7 649C 7F17 A086 DDEC During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell If a free society cannot help the many who are poor, it cannot save the few who are rich. -- John F. Kennedy ___ freebsd-current@freebsd.org mailto:freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org mailto:freebsd-current-unsubscr...@freebsd.org -- Etienne Robillard Company: Green Tea Hackers Club Occupation: Software Developer (and CEO) E-mail: e...@gthcfoundation.org Work phone: 450-936-2123 Website (Company): https://gthc.org/ Website (Blog): https://gthc.org/blog/ PGP public key fingerprint:F2A9 32EA 8E7C 460F 1728 A1A7 649C 7F17 A086 DDEC During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell If a free society cannot help the many who are poor, it cannot save the few who are rich. -- John F. Kennedy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFR]RT305xF support, w/o attachment
as far my knowledge goes, radiation from multi-frequency subcarriers in a multi-path system such as a wireless network (802.11 a/g/n) or a microwave oven is something you definitely want to avoid sitting in while hacking FreeBSD... https://gthc.org/wiki/Advisories/OFDM_20110315 I may have done technical errors but i do not drink in the morning!! :) FreeBSD doesn't define the wireless standards - other authorities (e.g. IEEE) do. Any standards involving RF radiation is tightly regulated in most countries, and the health authorities are aware of risks associated with large amounts of RF radiation. Since 802.11 a/g/n is internationally standardized (and permitted by the health authorities), we have to assume that the relevant standards are safe. I see no reason whatsoever why we should do anything special in FreeBSD here. Time for you to stop your anti-OFDM crusade and let FreeBSD developers work in peace. Steinar Haug, Nethelp consulting, sth...@nethelp.no ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFR]RT305xF support, w/o attachment
Date: Tue, 22 Mar 2011 06:46:12 -0400 From: Etienne Robillard e...@gthcfoundation.org Subject: Re: [CFR]RT305xF support, w/o attachment To: Adrian Chadd adr...@freebsd.org Cc: freebsd-current@freebsd.org Message-ID: 4d887df4.6060...@gthcfoundation.org Content-Type: text/plain; charset=ISO-8859-1 as far my knowledge goes, radiation from multi-frequency subcarriers in a multi-path system such as a wireless network (802.11 a/g/n) or a microwave oven is something you definitely want to avoid sitting in while hacking FreeBSD... https://gthc.org/wiki/Advisories/OFDM_20110315 I may have done technical errors but i do not drink in the morning!! :) On 22/03/11 06:30 AM, Adrian Chadd wrote: So I'm curious - what exactly about OFDM do you have a problem with? Adrian I have looked at your security advisory and also fail to understand what you are complaining about: Problem Description The OFDM (Orthogonal Frequency Division Multiplexing) modulation scheme as implemented in the upper 802.11 protocol for Wireless LAN (WLAN) networking is inherently insecure as designed to allow multi-frequency radiation of arbitrary Q-I numbers access in the unregulated ISM band/range. A high-Q signal has a very sharp peak and narrow pass-band. This lets the radio get past the noise floor using less transmitter energy. I am not sure what a Q-I number is. You use the word arbitrary. Are you claiming that OFDM allows the radios to exceed emission limits? As the other person commented, radio emmisions are regulated, even in the unlicensed spectrum. It would only be a security/safety issue if the radio exceeds legal limits. Your bounty suggests you have little/no evidence these limits are actually exceeded. A priviledge escalation exploit reprogramming a software-implemented radio to exceed radiation limits would be a concern, but it won't cook nearby users. The hardware would overheat before that happens. I agree excessive RF exposure should be avoided. I keep my wireless Access Point at its minimum power setting (1/4 power, 802.11g). Regards, James Phillips ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFR]RT305xF support, w/o attachment
On Monday 21 March 2011 00:16:01 Aleksandr Rybalko wrote: On Mon, 21 Mar 2011 05:59:45 +0800 Adrian Chadd adr...@freebsd.org wrote: On 21 March 2011 04:28, Sergey V. Dyatko sergey.dya...@gmail.com wrote: Last patch from Aleksandr 'works fine for me', so... may be rt2860 should be replaced to 'rt' for example ? rt0: flags= blah-blah-blah IHMO looks more .nice(?) than rt28600: flags= Yup, that's a good idea. Aleksandr, can you please do that? Off-course I can, but seems better name will be rtw or rtn, because we already have if_rt (for RT3052 ether) which have iface name rt. I think rtn is best. Maybe someone have better? rtw is a name for a Realtek driver. I'd prefer if can keep this driver in sync with the OpenBSD one where it is clearly derived from. So, rt28xx and rt30xx support has to be an extension to ral(4). That shouldn't be to hard to do, just throw in the code into dev/ral/ and hook it to the pci/ops code. -- Bernhard ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFR]RT305xF support, w/o attachment
Hi, On Mon, 21 Mar 2011 07:04:22 +0100 Bernhard Schmidt bschm...@freebsd.org wrote: On Monday 21 March 2011 00:16:01 Aleksandr Rybalko wrote: On Mon, 21 Mar 2011 05:59:45 +0800 Adrian Chadd adr...@freebsd.org wrote: On 21 March 2011 04:28, Sergey V. Dyatko sergey.dya...@gmail.com wrote: Last patch from Aleksandr 'works fine for me', so... may be rt2860 should be replaced to 'rt' for example ? rt0: flags= blah-blah-blah IHMO looks more .nice(?) than rt28600: flags= Yup, that's a good idea. Aleksandr, can you please do that? Off-course I can, but seems better name will be rtw or rtn, because we already have if_rt (for RT3052 ether) which have iface name rt. I think rtn is best. Maybe someone have better? rtw is a name for a Realtek driver. Realtek driver called urtw, but I agree with you to avoid confusion. I'd prefer if can keep this driver in sync with the OpenBSD one where it is clearly derived from. So, rt28xx and rt30xx support has to be an extension to ral(4). That shouldn't be to hard to do, just throw in the code into dev/ral/ and hook it to the pci/ops code. This driver closer to USB run(4), but this use USB and difference still big. In future, not so closer, I will try to join run, ral and my rt2860. But there is too much work and I need to find time for it. -- Bernhard So for now, best name is rtn. If no objections, I send updated patch with new name. Thank you Bernhard! WBW -- Alexandr Rybalko r...@dlink.ua aka Alex RAY r...@ddteam.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFR]RT305xF support, w/o attachment
On Monday, March 21, 2011 10:29:11 Aleksandr Rybalko wrote: Hi, On Mon, 21 Mar 2011 07:04:22 +0100 Bernhard Schmidt bschm...@freebsd.org wrote: On Monday 21 March 2011 00:16:01 Aleksandr Rybalko wrote: On Mon, 21 Mar 2011 05:59:45 +0800 Adrian Chadd adr...@freebsd.org wrote: On 21 March 2011 04:28, Sergey V. Dyatko sergey.dya...@gmail.com wrote: Last patch from Aleksandr 'works fine for me', so... may be rt2860 should be replaced to 'rt' for example ? rt0: flags= blah-blah-blah IHMO looks more .nice(?) than rt28600: flags= Yup, that's a good idea. Aleksandr, can you please do that? Off-course I can, but seems better name will be rtw or rtn, because we already have if_rt (for RT3052 ether) which have iface name rt. I think rtn is best. Maybe someone have better? rtw is a name for a Realtek driver. Realtek driver called urtw, but I agree with you to avoid confusion. That rtw driver I'm speaking of is for older Realtek 8180/8185 PCI based chips. Granted, not in our tree, but it exists. urtw(4) is for 8187B/L USB chipsets. I'd prefer if can keep this driver in sync with the OpenBSD one where it is clearly derived from. So, rt28xx and rt30xx support has to be an extension to ral(4). That shouldn't be to hard to do, just throw in the code into dev/ral/ and hook it to the pci/ops code. This driver closer to USB run(4), but this use USB and difference still big. In future, not so closer, I will try to join run, ral and my rt2860. But there is too much work and I need to find time for it. Please don't. There is a reason the PCI and USB chipsets, even if derived from the same base chipset, have different drivers. The BUS specific implementation/restrictions are way too different/important. Trying to merge those will only make your head ache :) So for now, best name is rtn. If no objections, I send updated patch with new name. I still don't think this is the way to go. Adding a totally independent driver now and replacing (or merging) it later simple won't work. Also, it is quite annoying from user point of view. I urge you to have a closer look at ral(4) and it's way of handling RT2500 and RT2600 specific differences. In it's simplest form you can copy the OpenBSD code 1:1 without any functional changes, heck, it's the source of this driver anyway. -- Bernhard ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFR]RT305xF support, w/o attachment
On Mon, 21 Mar 2011 11:00:49 +0100
Bernhard Schmidt bschm...@freebsd.org wrote:
On Monday, March 21, 2011 10:29:11 Aleksandr Rybalko wrote:
Hi,
On Mon, 21 Mar 2011 07:04:22 +0100
Bernhard Schmidt bschm...@freebsd.org wrote:
On Monday 21 March 2011 00:16:01 Aleksandr Rybalko wrote:
On Mon, 21 Mar 2011 05:59:45 +0800
Adrian Chadd adr...@freebsd.org wrote:
On 21 March 2011 04:28, Sergey V. Dyatko sergey.dya...@gmail.com
wrote:
Last patch from Aleksandr 'works fine for me', so... may be rt2860
should be replaced to 'rt' for example ?
rt0: flags= blah-blah-blah IHMO looks more .nice(?) than
rt28600: flags=
Yup, that's a good idea. Aleksandr, can you please do that?
Off-course I can, but seems better name will be rtw or rtn, because we
already have if_rt (for RT3052 ether) which have iface name rt.
I think rtn is best.
Maybe someone have better?
rtw is a name for a Realtek driver.
Realtek driver called urtw, but I agree with you to avoid confusion.
That rtw driver I'm speaking of is for older Realtek 8180/8185 PCI
based chips. Granted, not in our tree, but it exists. urtw(4) is for
8187B/L USB chipsets.
I'd prefer if can keep this driver in sync with the OpenBSD one where
it is clearly derived from. So, rt28xx and rt30xx support has to be an
extension to ral(4). That shouldn't be to hard to do, just throw in the
code into dev/ral/ and hook it to the pci/ops code.
This driver closer to USB run(4), but this use USB and difference still
big.
In future, not so closer, I will try to join run, ral and my rt2860. But
there is too much work and I need to find time for
it.
Please don't. There is a reason the PCI and USB chipsets, even if
derived from the same base chipset, have different drivers. The BUS
specific implementation/restrictions are way too different/important.
Trying to merge those will only make your head ache :)
So for now, best name is rtn.
If no objections, I send updated patch with new name.
I still don't think this is the way to go. Adding a totally independent
driver now and replacing (or merging) it later simple won't work. Also,
it is quite annoying from user point of view.
I urge you to have a closer look at ral(4) and it's way of handling
RT2500 and RT2600 specific differences. In it's simplest form you can
copy the OpenBSD code 1:1 without any functional changes, heck, it's
the source of this driver anyway.
--
Bernhard
I've look on difference between RT2[56]00 and RT2860 some time ago, but done it
again, and found that we can only place
RT2860/RT3090 support under same name (ral), but hardware have too big
difference. And in case I do this patch for RT3052F SoC,
when I placing RT2860 into ral, i get completely different driver (because SoC
don't use PCI interface).
So can You (or someone else) hint me, how to done this?
switch (what to do) {
case 'Remake run to support PCI and SoC interface':
Much work to make driver bus independent;
case 'Port OpenBSD one':
driver do not support SoC (SoC device don't have MCU);
break;
case 'Place my RT2860 under dev/ral':
different device in same driver;
break;
}
Hint me please.
WBW
--
Alexandr Rybalko r...@dlink.ua
aka Alex RAY r...@ddteam.net
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFR]RT305xF support, w/o attachment
So can You (or someone else) hint me, how to done this?
switch (what to do) {
case 'Remake run to support PCI and SoC interface':
Much work to make driver bus independent;
case 'Port OpenBSD one':
driver do not support SoC (SoC device don't have MCU);
break;
case 'Place my RT2860 under dev/ral':
different device in same driver;
break;
}
Hint me please.
WBW
Stop waffling please. I assume your not stupid and could perhaps
explains better what you
meant to say without the implicit assumptions you don't know what you're
doing.
--
Etienne Robillard
Company: Green Tea Hackers Club
Occupation: Software Developer (and CEO)
E-mail: e...@gthcfoundation.org
Work phone: 450-936-2123
Website (Company): https://gthc.org/
Website (Blog): https://gthc.org/blog/
PGP public key fingerprint:F2A9 32EA 8E7C 460F 1728 A1A7 649C 7F17 A086
DDEC
During times of universal deceit, telling the truth becomes a revolutionary
act. -- George Orwell
If a free society cannot help the many who are poor, it cannot save the few who
are rich. -- John F. Kennedy
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFR]RT305xF support, w/o attachment
on 21/03/2011 13:04 Etienne Robillard said the following:
So can You (or someone else) hint me, how to done this?
switch (what to do) {
case 'Remake run to support PCI and SoC interface':
Much work to make driver bus independent;
case 'Port OpenBSD one':
driver do not support SoC (SoC device don't have MCU);
break;
case 'Place my RT2860 under dev/ral':
different device in same driver;
break;
}
Hint me please.
WBW
Stop waffling please. I assume your not stupid and could perhaps
explains better what you
meant to say without the implicit assumptions you don't know what you're
doing.
I am not sure why this thread has deserved your attention - not everyone has as
good mastery of English as you do. And sometimes some people are more prone to
doubts.
Maybe you can give Aleksandr some help with the code in addition to your advice?
--
Andriy Gapon
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFR]RT305xF support, w/o attachment
I am not sure why this thread has deserved your attention - not everyone has as good mastery of English as you do. And sometimes some people are more prone to doubts. FYI im not very good in English as its not my main language too. However constructive comments are usually intelligible as opposed to unintelligible... ;-) Maybe you can give Aleksandr some help with the code in addition to your advice? In others words can we disable OFDM by default on the next-generation RTL8187 (rt2860) driver on FreeBSD? If not then I'd like suggesting Aleksandr a patch to add a 'WITHOUT_OFDM' and/or 'WITHOUT_FIRMWARE' option to disable compiling any BSD licensed driver code related to OFDM without the user explicit consent. kind regards, -- Etienne Robillard Company: Green Tea Hackers Club Occupation: Software Developer (and CEO) E-mail: e...@gthcfoundation.org Work phone: 450-936-2123 Website (Company): https://gthc.org/ Website (Blog): https://gthc.org/blog/ PGP public key fingerprint:F2A9 32EA 8E7C 460F 1728 A1A7 649C 7F17 A086 DDEC During times of universal deceit, telling the truth becomes a revolutionary act. -- George Orwell If a free society cannot help the many who are poor, it cannot save the few who are rich. -- John F. Kennedy ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFR]RT305xF support, w/o attachment
Hi all, I plan on tidying up the initial support patch (removing some of the stuff that snuck in from the ethernet, switch and wifi parts) and committing this sometime in the next week or so. I don't (yet) have hardware to test it myself. I'll just do a compile run and try to make sure it hasn't broken anything. I'll then take responsibility in case it breaks anything else in the build. Aleksandr will take responsibility for fixing bugs. :) Thankyou for your hard work Aleksandr! Adrian On 14 March 2011 22:29, Aleksandr Rybalko r...@dlink.ua wrote: Hello, all. I am pleased to present support for Ralink RT3050F/RT3052F MIPS SoC's for FreeBSD. This patches add support of 1. GPIO/Interrupt/System/UART controllers + internal bus http://my.ddteam.net/files/2011-03-14_RT305xF_support.patch 2. RT305xF embedded ethernet controller http://my.ddteam.net/files/2011-03-14_RT305xF_ether_support.patch 3. RT2860 802.11n controller authors Damien Bergamini and Alexander Egorenkov http://my.ddteam.net/files/2011-03-14_rt2860.patch only modification to work with RT2872 (embedded to RT305[02]F) wrote by me. Also supported DWC like USB OTG controller, not included now, because have many issues: 1. Don't support SPIT transactions (FS device on HS Hub) yet. 2. Don't support ISOC transactions yet. 3. And have problems with some devices, possibly timing problem. You can found it at http://my.ddteam.net/hg/BASE/file/dd632189c3a0/head/sys/dev/usb/controller/ files dotg* Also supported internal switch, not included now, because this part of not done Switch API project. You can found it at http://my.ddteam.net/hg/BASE/file/dd632189c3a0/head/sys/dev/switch/ Remaining issues: RT2860 support only Open(no crypto) mode for RT305[02]F Comments are welcome. Want to know, what I do right or what wrong :) -- Alexandr Rybalko r...@dlink.ua aka Alex RAY r...@ddteam.net ___ freebsd-m...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-mips To unsubscribe, send any mail to freebsd-mips-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFR]RT305xF support, w/o attachment
On Sun, 20 Mar 2011 23:31:51 +0800 Adrian Chadd adr...@freebsd.org wrote: Hi all, Hi, Adrian I plan on tidying up the initial support patch (removing some of the stuff that snuck in from the ethernet, switch and wifi parts) and committing this sometime in the next week or so. I don't (yet) have hardware to test it myself. I'll just do a compile run and try to make sure it hasn't broken anything. I'll then take responsibility in case it breaks anything else in the build. Aleksandr will take responsibility for fixing bugs. :) Thankyou for your hard work Aleksandr! Last patch from Aleksandr 'works fine for me', so... may be rt2860 should be replaced to 'rt' for example ? rt0: flags= blah-blah-blah IHMO looks more .nice(?) than rt28600: flags= Adrian On 14 March 2011 22:29, Aleksandr Rybalko r...@dlink.ua wrote: Hello, all. I am pleased to present support for Ralink RT3050F/RT3052F MIPS SoC's for FreeBSD. This patches add support of 1. GPIO/Interrupt/System/UART controllers + internal bus http://my.ddteam.net/files/2011-03-14_RT305xF_support.patch 2. RT305xF embedded ethernet controller http://my.ddteam.net/files/2011-03-14_RT305xF_ether_support.patch 3. RT2860 802.11n controller authors Damien Bergamini and Alexander Egorenkov http://my.ddteam.net/files/2011-03-14_rt2860.patch only modification to work with RT2872 (embedded to RT305[02]F) wrote by me. Also supported DWC like USB OTG controller, not included now, because have many issues: 1. Don't support SPIT transactions (FS device on HS Hub) yet. 2. Don't support ISOC transactions yet. 3. And have problems with some devices, possibly timing problem. You can found it at http://my.ddteam.net/hg/BASE/file/dd632189c3a0/head/sys/dev/usb/controller/ files dotg* Also supported internal switch, not included now, because this part of not done Switch API project. You can found it at http://my.ddteam.net/hg/BASE/file/dd632189c3a0/head/sys/dev/switch/ Remaining issues: RT2860 support only Open(no crypto) mode for RT305[02]F Comments are welcome. Want to know, what I do right or what wrong :) -- Alexandr Rybalko r...@dlink.ua aka Alex RAY r...@ddteam.net -- wbr, tiger ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFR]RT305xF support, w/o attachment
On 21 March 2011 04:28, Sergey V. Dyatko sergey.dya...@gmail.com wrote: Last patch from Aleksandr 'works fine for me', so... may be rt2860 should be replaced to 'rt' for example ? rt0: flags= blah-blah-blah IHMO looks more .nice(?) than rt28600: flags= Yup, that's a good idea. Aleksandr, can you please do that? Adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFR]RT305xF support, w/o attachment
On Mon, 21 Mar 2011 05:59:45 +0800 Adrian Chadd adr...@freebsd.org wrote: On 21 March 2011 04:28, Sergey V. Dyatko sergey.dya...@gmail.com wrote: Last patch from Aleksandr 'works fine for me', so... may be rt2860 should be replaced to 'rt' for example ? rt0: flags= blah-blah-blah IHMO looks more .nice(?) than rt28600: flags= Yup, that's a good idea. Aleksandr, can you please do that? Off-course I can, but seems better name will be rtw or rtn, because we already have if_rt (for RT3052 ether) which have iface name rt. I think rtn is best. Maybe someone have better? Adrian -- Aleksandr Rybalko r...@ddteam.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFR]RT305xF support, w/o attachment
Is someone able to help me hunt down a mini-PCIe ralink card? I'd like to help Aleksandr include his SoC MIPS stuff to FreeBSD and as part of that I'd like to try and make this wireless driver work on supported PCI/PCIe cards. But I completely lack the hardware to do so, and I lack the time to hunt down hardware (and money to buy another EEEPC just to do it.) Thanks, adrian On 17 March 2011 01:06, Jan Henrik Sylvester m...@janh.de wrote: Hello! On 01/-10/-28163 20:59, Aleksandr Rybalko wrote: 3. RT2860 802.11n controller authors Damien Bergamini and Alexander Egorenkov http://my.ddteam.net/files/2011-03-14_rt2860.patch only modification to work with RT2872 (embedded to RT305[02]F) wrote by me. Is this supposed to work on its own bringing support for Ralink 2860 to FreeBSD? (The one in the Asus EeePC 901/1000H according to http://wiki.freebsd.org/AsusEee .) Remaining issues: RT2860 support only Open(no crypto) mode for RT305[02]F Does this mean WPA should work for RT2860? (Just not for the chips you added support for?) If this is supposed to bring RT2860 support to FreeBSD in general: - Should it work on amd64 and i386? - Should it work on 8.2-RELEASE? - Should it work as a module? In case this is all supposed to work: I tried to create a module on 8.2-RELEASE/amd64 by adding a simple sys/modules/rt2860/Makefile (as I did not want to modify my stock 8.2-RELEASE kernel). I only got to: In file included from /usr/src/sys/modules/rt2860/../../dev/rt2860/rt2860.c:19: @/dev/rt2860/rt2860_softc.h:52:24: error: opt_rt2860.h: No such file or directory I do not find opt_rt2860.h anywhere in your patches. Assuming it was optional, I have commented it out only to get to: cc1: warnings being treated as errors /usr/src/sys/modules/rt2860/../../dev/rt2860/rt2860_pci.c:63: warning: 'rt2860_pci_detach' declared 'static' but never defined Probably, I am doing something unsupported here (especially as there is no if_rt2860_pci.c, which I would expect). Cheers, Jan Henrik ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFR]RT305xF support, w/o attachment
On Thu, 17 Mar 2011 15:45:26 +0800 Adrian Chadd adr...@freebsd.org wrote: Is someone able to help me hunt down a mini-PCIe ralink card? I'd like to help Aleksandr include his SoC MIPS stuff to FreeBSD and as part of that I'd like to try and make this wireless driver work on supported PCI/PCIe cards. But I completely lack the hardware to do so, and I lack the time to hunt down hardware (and money to buy another EEEPC just to do it.) Thanks, Hi, I have rt3090 on my laptop (running HEAD, i386) and I can take part in testing none1@pci0:3:0:0: class=0x028000 card=0x30901814 chip=0x30901814 rev=0x00 hdr=0x00 vendor = 'Ralink Technology, Corp.' class = network adrian On 17 March 2011 01:06, Jan Henrik Sylvester m...@janh.de wrote: Hello! On 01/-10/-28163 20:59, Aleksandr Rybalko wrote: 3. RT2860 802.11n controller authors Damien Bergamini and Alexander Egorenkov http://my.ddteam.net/files/2011-03-14_rt2860.patch only modification to work with RT2872 (embedded to RT305[02]F) wrote by me. Is this supposed to work on its own bringing support for Ralink 2860 to FreeBSD? (The one in the Asus EeePC 901/1000H according to http://wiki.freebsd.org/AsusEee .) Remaining issues: RT2860 support only Open(no crypto) mode for RT305[02]F Does this mean WPA should work for RT2860? (Just not for the chips you added support for?) If this is supposed to bring RT2860 support to FreeBSD in general: - Should it work on amd64 and i386? - Should it work on 8.2-RELEASE? - Should it work as a module? In case this is all supposed to work: I tried to create a module on 8.2-RELEASE/amd64 by adding a simple sys/modules/rt2860/Makefile (as I did not want to modify my stock 8.2-RELEASE kernel). I only got to: In file included from /usr/src/sys/modules/rt2860/../../dev/rt2860/rt2860.c:19: @/dev/rt2860/rt2860_softc.h:52:24: error: opt_rt2860.h: No such file or directory I do not find opt_rt2860.h anywhere in your patches. Assuming it was optional, I have commented it out only to get to: cc1: warnings being treated as errors /usr/src/sys/modules/rt2860/../../dev/rt2860/rt2860_pci.c:63: warning: 'rt2860_pci_detach' declared 'static' but never defined Probably, I am doing something unsupported here (especially as there is no if_rt2860_pci.c, which I would expect). Cheers, Jan Henrik -- wbr, tiger ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFR]RT305xF support, w/o attachment
Cool! You've just volunteered to help Aleksandr at least get the driver compiling, probing and attaching. :) I'll review and commit something to head when you have it somewhat working, ok? :) Adrian (Cool, I can get back to fixing if_ath issues.) On 17 March 2011 16:08, Sergey V. Dyatko sergey.dya...@gmail.com wrote: On Thu, 17 Mar 2011 15:45:26 +0800 Adrian Chadd adr...@freebsd.org wrote: Is someone able to help me hunt down a mini-PCIe ralink card? I'd like to help Aleksandr include his SoC MIPS stuff to FreeBSD and as part of that I'd like to try and make this wireless driver work on supported PCI/PCIe cards. But I completely lack the hardware to do so, and I lack the time to hunt down hardware (and money to buy another EEEPC just to do it.) Thanks, Hi, I have rt3090 on my laptop (running HEAD, i386) and I can take part in testing none1@pci0:3:0:0: class=0x028000 card=0x30901814 chip=0x30901814 rev=0x00 hdr=0x00 vendor = 'Ralink Technology, Corp.' class = network adrian On 17 March 2011 01:06, Jan Henrik Sylvester m...@janh.de wrote: Hello! On 01/-10/-28163 20:59, Aleksandr Rybalko wrote: 3. RT2860 802.11n controller authors Damien Bergamini and Alexander Egorenkov http://my.ddteam.net/files/2011-03-14_rt2860.patch only modification to work with RT2872 (embedded to RT305[02]F) wrote by me. Is this supposed to work on its own bringing support for Ralink 2860 to FreeBSD? (The one in the Asus EeePC 901/1000H according to http://wiki.freebsd.org/AsusEee .) Remaining issues: RT2860 support only Open(no crypto) mode for RT305[02]F Does this mean WPA should work for RT2860? (Just not for the chips you added support for?) If this is supposed to bring RT2860 support to FreeBSD in general: - Should it work on amd64 and i386? - Should it work on 8.2-RELEASE? - Should it work as a module? In case this is all supposed to work: I tried to create a module on 8.2-RELEASE/amd64 by adding a simple sys/modules/rt2860/Makefile (as I did not want to modify my stock 8.2-RELEASE kernel). I only got to: In file included from /usr/src/sys/modules/rt2860/../../dev/rt2860/rt2860.c:19: @/dev/rt2860/rt2860_softc.h:52:24: error: opt_rt2860.h: No such file or directory I do not find opt_rt2860.h anywhere in your patches. Assuming it was optional, I have commented it out only to get to: cc1: warnings being treated as errors /usr/src/sys/modules/rt2860/../../dev/rt2860/rt2860_pci.c:63: warning: 'rt2860_pci_detach' declared 'static' but never defined Probably, I am doing something unsupported here (especially as there is no if_rt2860_pci.c, which I would expect). Cheers, Jan Henrik -- wbr, tiger ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFR]RT305xF support, w/o attachment
On Thu, 17 Mar 2011 16:57:49 +0800 Adrian Chadd adr...@freebsd.org wrote: Cool! You've just volunteered to help Aleksandr at least get the driver compiling, probing and attaching. :) I'll review and commit something to head when you have it somewhat working, ok? :) sure, cause I tired look at panics after `kldload rt2860_sys` (ndis) ~3 of 4 times :-) For example: http://tiger.ipfw.ru/files/core_1.txt Adrian (Cool, I can get back to fixing if_ath issues.) On 17 March 2011 16:08, Sergey V. Dyatko sergey.dya...@gmail.com wrote: On Thu, 17 Mar 2011 15:45:26 +0800 Adrian Chadd adr...@freebsd.org wrote: Is someone able to help me hunt down a mini-PCIe ralink card? I'd like to help Aleksandr include his SoC MIPS stuff to FreeBSD and as part of that I'd like to try and make this wireless driver work on supported PCI/PCIe cards. But I completely lack the hardware to do so, and I lack the time to hunt down hardware (and money to buy another EEEPC just to do it.) Thanks, Hi, I have rt3090 on my laptop (running HEAD, i386) and I can take part in testing none1@pci0:3:0:0: class=0x028000 card=0x30901814 chip=0x30901814 rev=0x00 hdr=0x00 vendor = 'Ralink Technology, Corp.' class = network adrian On 17 March 2011 01:06, Jan Henrik Sylvester m...@janh.de wrote: Hello! On 01/-10/-28163 20:59, Aleksandr Rybalko wrote: 3. RT2860 802.11n controller authors Damien Bergamini and Alexander Egorenkov http://my.ddteam.net/files/2011-03-14_rt2860.patch only modification to work with RT2872 (embedded to RT305[02]F) wrote by me. Is this supposed to work on its own bringing support for Ralink 2860 to FreeBSD? (The one in the Asus EeePC 901/1000H according to http://wiki.freebsd.org/AsusEee .) Remaining issues: RT2860 support only Open(no crypto) mode for RT305[02]F Does this mean WPA should work for RT2860? (Just not for the chips you added support for?) If this is supposed to bring RT2860 support to FreeBSD in general: - Should it work on amd64 and i386? - Should it work on 8.2-RELEASE? - Should it work as a module? In case this is all supposed to work: I tried to create a module on 8.2-RELEASE/amd64 by adding a simple sys/modules/rt2860/Makefile (as I did not want to modify my stock 8.2-RELEASE kernel). I only got to: In file included from /usr/src/sys/modules/rt2860/../../dev/rt2860/rt2860.c:19: @/dev/rt2860/rt2860_softc.h:52:24: error: opt_rt2860.h: No such file or directory I do not find opt_rt2860.h anywhere in your patches. Assuming it was optional, I have commented it out only to get to: cc1: warnings being treated as errors /usr/src/sys/modules/rt2860/../../dev/rt2860/rt2860_pci.c:63: warning: 'rt2860_pci_detach' declared 'static' but never defined Probably, I am doing something unsupported here (especially as there is no if_rt2860_pci.c, which I would expect). Cheers, Jan Henrik -- wbr, tiger -- wbr, tiger ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFR]RT305xF support, w/o attachment
Hi again! On Wed, 16 Mar 2011 20:44:05 +0200 Aleksandr Rybalko r...@ddteam.net wrote: Hi, On Wed, 16 Mar 2011 18:06:59 +0100 Jan Henrik Sylvester m...@janh.de wrote: Hello! On 01/-10/-28163 20:59, Aleksandr Rybalko wrote: 3. RT2860 802.11n controller authors Damien Bergamini and Alexander Egorenkov http://my.ddteam.net/files/2011-03-14_rt2860.patch only modification to work with RT2872 (embedded to RT305[02] F) wrote by me. Is this supposed to work on its own bringing support for Ralink 2860 to FreeBSD? (The one in the Asus EeePC 901/1000H according to http://wiki.freebsd.org/AsusEee .) Remaining issues: RT2860 support only Open(no crypto) mode for RT305[02]F Does this mean WPA should work for RT2860? (Just not for the chips you added support for?) As I know this driver support WPA, but best place to read/ask about this on this thread http://forums.freebsd.org/showthread.php?t=7010 If this is supposed to bring RT2860 support to FreeBSD in general: - Should it work on amd64 and i386? - Should it work on 8.2-RELEASE? - Should it work as a module? In case this is all supposed to work: I tried to create a module on 8.2-RELEASE/amd64 by adding a simple sys/modules/rt2860/Makefile (as I did not want to modify my stock 8.2-RELEASE kernel). I only got to: In file included from /usr/src/sys/modules/rt2860/../../dev/rt2860/rt2860.c:19: @/dev/rt2860/rt2860_softc.h:52:24: error: opt_rt2860.h: No such file or directory I do not find opt_rt2860.h anywhere in your patches. Assuming it was optional, I have commented it out only to get to: cc1: warnings being treated as errors /usr/src/sys/modules/rt2860/../../dev/rt2860/rt2860_pci.c:63: warning: 'rt2860_pci_detach' declared 'static' but never defined Probably, I am doing something unsupported here (especially as there is no if_rt2860_pci.c, which I would expect). No, it's me. Too much data, so I a little confused here. Patch targeting to start support RT3052F/RT3050F System on Chip. Which main part for embedded systems like routers, AP etc. To get it compiled need remove 'rt2860_pci_detach' declaration, because pci and obio interfaces have same detach device methods (rt2860_detach in rt2860.c) And opt_rt2860.h must be defined in sys/conf/options code # options for the Ralink RT286x driver (rt2860) RT2860_DEBUGopt_rt2860.h /code Cheers, Jan Henrik I will remake patch tomorrow. Fixed patch here http://my.ddteam.net/files/2011-03-17_rt2860.patch Thanks for your report and questions? -- Aleksandr Rybalko r...@ddteam.net Many thanks for help. -- Alexandr Rybalko r...@dlink.ua aka Alex RAY r...@ddteam.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFR]RT305xF support, w/o attachment
On Thu, 17 Mar 2011 13:26:16 +0200
Aleksandr Rybalko r...@dlink.ua wrote:
Hi again!
On Wed, 16 Mar 2011 20:44:05 +0200
Aleksandr Rybalko r...@ddteam.net wrote:
Hi,
On Wed, 16 Mar 2011 18:06:59 +0100
Jan Henrik Sylvester m...@janh.de wrote:
Hello!
On 01/-10/-28163 20:59, Aleksandr Rybalko wrote:
3. RT2860 802.11n controller authors Damien Bergamini and
Alexander Egorenkov
http://my.ddteam.net/files/2011-03-14_rt2860.patch only
modification to work with RT2872 (embedded to RT305[02] F)
wrote by me.
Is this supposed to work on its own bringing support for Ralink
2860 to FreeBSD? (The one in the Asus EeePC 901/1000H according
to http://wiki.freebsd.org/AsusEee .)
Remaining issues:
RT2860 support only Open(no crypto) mode for RT305[02]F
Does this mean WPA should work for RT2860? (Just not for the
chips you added support for?)
As I know this driver support WPA, but best place to read/ask about
this on this thread http://forums.freebsd.org/showthread.php?t=7010
If this is supposed to bring RT2860 support to FreeBSD in
general:
- Should it work on amd64 and i386?
- Should it work on 8.2-RELEASE?
- Should it work as a module?
In case this is all supposed to work: I tried to create a module
on 8.2-RELEASE/amd64 by adding a simple
sys/modules/rt2860/Makefile (as I did not want to modify my
stock 8.2-RELEASE kernel). I only got to:
In file included from
/usr/src/sys/modules/rt2860/../../dev/rt2860/rt2860.c:19:
@/dev/rt2860/rt2860_softc.h:52:24: error: opt_rt2860.h: No such
file or directory
I do not find opt_rt2860.h anywhere in your patches. Assuming it
was optional, I have commented it out only to get to:
cc1: warnings being treated as errors
/usr/src/sys/modules/rt2860/../../dev/rt2860/rt2860_pci.c:63:
warning: 'rt2860_pci_detach' declared 'static' but never defined
Probably, I am doing something unsupported here (especially as
there is no if_rt2860_pci.c, which I would expect).
No, it's me. Too much data, so I a little confused here.
Patch targeting to start support RT3052F/RT3050F System on Chip.
Which main part for embedded systems like routers, AP etc.
To get it compiled need remove 'rt2860_pci_detach' declaration,
because pci and obio interfaces have same detach device methods
(rt2860_detach in rt2860.c)
And opt_rt2860.h must be defined in sys/conf/options
code
# options for the Ralink RT286x driver (rt2860)
RT2860_DEBUGopt_rt2860.h
/code
Cheers,
Jan Henrik
I will remake patch tomorrow.
Fixed patch here http://my.ddteam.net/files/2011-03-17_rt2860.patch
include opt_rt2860.h still here (rt2860_softc.h), I removed it, write
simple Makefile:
laptop# cat Makefile
# $FreeBSD$
.PATH: ${.CURDIR}/../../dev/rt2860
KMOD= if_rt2860
SRCS= rt2860.c
SRCS+= device_if.h bus_if.h pci_if.h
.include bsd.kmod.mk
laptop# pwd
/usr/src/sys/modules/rt2860
laptop# make
Warning: Object directory not changed from
original /usr/src/sys/modules/rt2860 @ - /usr/src/sys
machine - /usr/src/sys/i386/include
x86 - /usr/src/sys/x86/include
awk -f @/tools/makeobjops.awk @/kern/device_if.m -h
awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h
awk -f @/tools/makeobjops.awk @/dev/pci/pci_if.m -h
cc -O2 -pipe -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE
-nostdinc -I. -I@ -I@/contrib/altq -finline-limit=8000 --param
inline-unit-growth=100 --param large-function-growth=1000 -fno-common
-mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx
-mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -ffreestanding
-fstack-protector -std=iso9899:1999 -fstack-protector -Wall
-Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef
-Wno-pointer-sign -fformat-extensions
-c /usr/src/sys/modules/rt2860/../../dev/rt2860/rt2860.c ld -d
-warn-common -r -d -o if_rt2860.kld rt2860.o : export_syms awk
-f /usr/src/sys/modules/rt2860/../../conf/kmod_syms.awk if_rt2860.kld
export_syms | xargs -J% objcopy % if_rt2860.kld ld -Bshareable -d
-warn-common -o if_rt2860.ko if_rt2860.kld objcopy --strip-debug
if_rt2860.ko
laptop# kldload ./if_rt2860.ko
kldload: can't load ./if_rt2860.ko: No such file or directory
dmesg: link_elf: symbol rt2860_io_mac_write undefined
p.s. let me know if you need any additional information
Thanks for your report and questions?
--
Aleksandr Rybalko r...@ddteam.net
Many thanks for help.
--
---
Sergey V Dyatko aka tiger | sergey.dya...@gmail.com
/\ ASCII Ribbon Campaign | FreeBSD Since 4.x
\ / - NO HTML/RTF in e-mail | http://tiger.bsd.by
X - NO Word docs in e-mail | XMPP: ti...@jabber.org.by
/ \
---
Re: [CFR]RT305xF support, w/o attachment
Hello! On 01/-10/-28163 20:59, Aleksandr Rybalko wrote: 3. RT2860 802.11n controller authors Damien Bergamini and Alexander Egorenkov http://my.ddteam.net/files/2011-03-14_rt2860.patch only modification to work with RT2872 (embedded to RT305[02]F) wrote by me. Is this supposed to work on its own bringing support for Ralink 2860 to FreeBSD? (The one in the Asus EeePC 901/1000H according to http://wiki.freebsd.org/AsusEee .) Remaining issues: RT2860 support only Open(no crypto) mode for RT305[02]F Does this mean WPA should work for RT2860? (Just not for the chips you added support for?) If this is supposed to bring RT2860 support to FreeBSD in general: - Should it work on amd64 and i386? - Should it work on 8.2-RELEASE? - Should it work as a module? In case this is all supposed to work: I tried to create a module on 8.2-RELEASE/amd64 by adding a simple sys/modules/rt2860/Makefile (as I did not want to modify my stock 8.2-RELEASE kernel). I only got to: In file included from /usr/src/sys/modules/rt2860/../../dev/rt2860/rt2860.c:19: @/dev/rt2860/rt2860_softc.h:52:24: error: opt_rt2860.h: No such file or directory I do not find opt_rt2860.h anywhere in your patches. Assuming it was optional, I have commented it out only to get to: cc1: warnings being treated as errors /usr/src/sys/modules/rt2860/../../dev/rt2860/rt2860_pci.c:63: warning: 'rt2860_pci_detach' declared 'static' but never defined Probably, I am doing something unsupported here (especially as there is no if_rt2860_pci.c, which I would expect). Cheers, Jan Henrik ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: [CFR]RT305xF support, w/o attachment
Hi, On Wed, 16 Mar 2011 18:06:59 +0100 Jan Henrik Sylvester m...@janh.de wrote: Hello! On 01/-10/-28163 20:59, Aleksandr Rybalko wrote: 3. RT2860 802.11n controller authors Damien Bergamini and Alexander Egorenkov http://my.ddteam.net/files/2011-03-14_rt2860.patch only modification to work with RT2872 (embedded to RT305[02] F) wrote by me. Is this supposed to work on its own bringing support for Ralink 2860 to FreeBSD? (The one in the Asus EeePC 901/1000H according to http://wiki.freebsd.org/AsusEee .) Remaining issues: RT2860 support only Open(no crypto) mode for RT305[02]F Does this mean WPA should work for RT2860? (Just not for the chips you added support for?) As I know this driver support WPA, but best place to read/ask about this on this thread http://forums.freebsd.org/showthread.php?t=7010 If this is supposed to bring RT2860 support to FreeBSD in general: - Should it work on amd64 and i386? - Should it work on 8.2-RELEASE? - Should it work as a module? In case this is all supposed to work: I tried to create a module on 8.2-RELEASE/amd64 by adding a simple sys/modules/rt2860/Makefile (as I did not want to modify my stock 8.2-RELEASE kernel). I only got to: In file included from /usr/src/sys/modules/rt2860/../../dev/rt2860/rt2860.c:19: @/dev/rt2860/rt2860_softc.h:52:24: error: opt_rt2860.h: No such file or directory I do not find opt_rt2860.h anywhere in your patches. Assuming it was optional, I have commented it out only to get to: cc1: warnings being treated as errors /usr/src/sys/modules/rt2860/../../dev/rt2860/rt2860_pci.c:63: warning: 'rt2860_pci_detach' declared 'static' but never defined Probably, I am doing something unsupported here (especially as there is no if_rt2860_pci.c, which I would expect). No, it's me. Too much data, so I a little confused here. Patch targeting to start support RT3052F/RT3050F System on Chip. Which main part for embedded systems like routers, AP etc. To get it compiled need remove 'rt2860_pci_detach' declaration, because pci and obio interfaces have same detach device methods (rt2860_detach in rt2860.c) And opt_rt2860.h must be defined in sys/conf/options code # options for the Ralink RT286x driver (rt2860) RT2860_DEBUGopt_rt2860.h /code Cheers, Jan Henrik I will remake patch tomorrow. Thanks for your report and questions? -- Aleksandr Rybalko r...@ddteam.net ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
