Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

T2 completeness tracking #70

Closed
22 of 39 tasks
Frijol opened this issue Jul 7, 2015 · 5 comments
Closed
22 of 39 tasks

T2 completeness tracking #70

Frijol opened this issue Jul 7, 2015 · 5 comments

Comments

@Frijol
Copy link
Member

Frijol commented Jul 7, 2015

This issue is for tracking T2 features which must be completed before ship. Discuss below what should/shouldn't be on this list.

Hardware

  • Final hardware design
  • Pilot batch of 100
  • FCC cert
  • CE cert
  • Full manufacturing

Firmware

OpenWRT

  • BLE drivers
  • audio/video drivers
  • flash drive mounting drivers
  • 3g/4g dongle integration

CLI

Milestone tracking here

I'm not including t2 status, t2 ap, or t2 root command because, although they are super awesome features, they aren't absolutely critical to shipping.

Docs

Start

Milestone tracking

Modules working/documented

Language Support

Platform support

@flaki
Copy link

flaki commented Jul 11, 2015

How about platform support? I noticed the other day that t2-cli doesn't work on Windows (at least, for me). Are we aiming for Windows platform support for the t2, and if yes, what is the timing? (launch? later?). If the answer is yes, it should be tracked above, too, I think.

@Frijol
Copy link
Member Author

Frijol commented Jul 13, 2015

Ah, good point. @johnnyman727 do you know the status of t2-cli on Windows? I haven't tried it but know that t2 provision has unix reliance with current implementation

@johnnyman727
Copy link
Contributor

@Frijol you have it exactly right.

@Frijol
Copy link
Member Author

Frijol commented Sep 4, 2015

Timeline update:
We think we have a software fix in for the FCC certification issue that has been blocking us, as well as a hardware fix for a CE certification. The fixes are currently in testing, and we should hear back any day.
Since the CE issue fix is hardware, Tessel 2 requires another board revision. These revised boards will then be sent in again for FCC and CE certification. This takes 2-3 weeks.
It will then take another 6 weeks or so to ramp up into full manufacturing and get them shipped.

@Frijol
Copy link
Member Author

Frijol commented Jan 25, 2016

Deprecated, #106 is more useful for this

@Frijol Frijol closed this as completed Jan 25, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants