Username
Fuckass
I didn't know that it required license fees. Good to know though, I guess.
Last edited by a moderator:
'conso' said:Now that we are on licensing fees, what about the fvat-patents? TomTom was recently sued by Microsoft for those. If it was my decision, I'd stick to ext2 and remove fvat from the base-kernel (i guess a fvat-module could still be made available for download, similar to how codecs are handled), but that's not my decision. Just wanted to warn before unnecessery costs come up.
Interesting idea, don't see how it could hurt Pandora in any way going to 8.3 filenames only (for fat).
It also doesn't work 1/2 the time, and is only for permanent mounted hard drives, temp things like sd would fail hard.'cb88' said:well there is always the ext2 drivers for windows.... I know it has drawbacks (like you acutally have to install it ) might not be as stable as fat support in windows doubt that though
Isn't FAT32 only used on SD cards? And don't SD card manufacturers license those patents from Microsoft?'conso' said:Now that we are on licensing fees, what about the fvat-patents? TomTom was recently sued by Microsoft for those. If it was my decision, I'd stick to ext2 and remove fvat from the base-kernel (i guess a fvat-module could still be made available for download, similar to how codecs are handled), but that's not my decision. Just wanted to warn before unnecessery costs come up.
It seems that some of you should make apologies to spaceballs3000, and a few thanks for pointing this out for the OP team.'MWeston' said:TI has said that customers are responsible for licensing of the SD protocol so we'll have to pay for it. At least we can use their logo now.
'BackAssward' said:It seems that some of you should make apologies to spaceballs3000, and a few thanks for pointing this out for the OP team.'MWeston' said:TI has said that customers are responsible for licensing of the SD protocol so we'll have to pay for it. At least we can use their logo now.
(not talking to MWeston, but the "internet know it alls" who argued this without knowing what they were talking about.
btw, thanks spaceballs3000
Read the posts again - nobody flamed him or outright stated that he was absolutely wrong (at least, I didn't). All I said was that I wouldn't expect it to be that way. Everything was stated as opinion, not researched (or assumed) fact.
EDIT: Good to know that this is covered now and we didn't run into some potentially fatal licensing fees.
+1 and Amen to that!'Alpha2' said:the licensing fees already look kinda painful at this point, I'm really hopeing there's a decent enough warchest set up to pay for all these things now and not forcing the team to come out of their own pockets even further for unplanned expenses.
'Alpha2' said:the licensing fees already look kinda painful at this point, I'm really hopeing there's a decent enough warchest set up to pay for all these things now and not forcing the team to come out of their own pockets even further for unplanned expenses.
From other posts I've read, I think they got the major ones planned, CE & FCC (SAR if wireless is not a separate pre-certified module).
Though they should do UL if they can, since it's an liability issue, it be on my personal list.
If they are not using pre-certified wireless modules then get Industry Canada (IC) for Canada, usually this can be tacked on as part of FCC cost for a little bit more.
China Compulsory Certification (CCC) if selling in china.
etc...
If this has to be "worked around",'Vorporeal' said:I wonder if the vfat stuff could be solved by not providing it on the device when it's shipped, but having a launch-day firmware update that just overwrites the kernel with another that has vfat support in it? Something like that might work... who knows.