azonenberg_work has quit [Ping timeout: 260 seconds]
OmniMancer has joined ##openfpga
Bike has quit [Quit: Lost terminal]
pie_ has joined ##openfpga
Jybz has joined ##openfpga
emeb_mac has quit [Quit: Leaving.]
Asu has joined ##openfpga
ZombieChicken has quit [Ping timeout: 260 seconds]
AndrevS has joined ##openfpga
Asu has quit [Remote host closed the connection]
rombik_su has joined ##openfpga
rohitksingh has quit [Ping timeout: 260 seconds]
GenTooMan has joined ##openfpga
Asu has joined ##openfpga
OmniMancer has quit [Quit: Leaving.]
lutsabound has joined ##openfpga
rvense has joined ##openfpga
_whitelogger has joined ##openfpga
Asu has quit [Remote host closed the connection]
emeb has joined ##openfpga
Asu has joined ##openfpga
<whitequark>
huh, 100BASE-T4 is pretty wack
<gruetzkopf>
yep
<gruetzkopf>
hm, $chinese_ebay_seller was fast, the cursed 8051s arrived yesterday
<GenTooMan>
what?! 8051 well at least you can get a compiler for it.
<OK_b00m3r>
true!
<OK_b00m3r>
why are they cursed gruetzkopf
<sensille>
oh, i still have some, i think. and 8049
<GenTooMan>
probably because the arch has been replaced by something easier to use and more straight forward the 8049 was definitely cursed
<GenTooMan>
I only had to touch those to make a assembly traslator for ancient product
<OK_b00m3r>
fair enough. i have no 8051 exp, just pic18, atmel 328, arm cortex-m0+ mainly
<GenTooMan>
bank switch IO and program space crazy pointers and a tiny stack (128 bytes max)
<sensille>
(only found 8749 in my box)
<gruetzkopf>
people i know have a whole bunch of MCS-48 parts in production still
<gruetzkopf>
(and i also commonly see 8085 with more than 2 MByte of banked memory.. (64k address space!)
<whitequark>
8051 is still not as bad as 8-bit PICs
<GenTooMan>
very true newer pics are OK but not that fun (IE they aren't a nice address space like ARM)
<whitequark>
also, you don't bank switch IO on 8051
<whitequark>
you have register banks (only really useful for interrupts, and marginally at that), and if you need more than 64K of code or RAM, some system-specific way to bank that too
<GenTooMan>
I think what I meant was memory mapped IO with bank switched memory. I try to forget these things.
<whitequark>
not in the base 8051 arch, no
<whitequark>
maybe you had a variant that specifically did it
ym has joined ##openfpga
X-Scale has quit [Ping timeout: 265 seconds]
X-Scale` has joined ##openfpga
rombik_su has quit [Read error: Connection reset by peer]
emeb_mac has joined ##openfpga
gregdavill has quit [Quit: Leaving]
lutsabound has quit [Quit: Connection closed for inactivity]
<whitequark>
hm
<whitequark>
how come 100BASE-T2 implements collision detection if it's full duplex over both pairs?
<whitequark>
doesn't that mean it can't have collisions by definition?
<whitequark>
is that for... hubs?
<whitequark>
also, what the heck is 100BASE-TX half duplex?
<mwk>
well if you have a 100BASE-TX
<mwk>
that is perfectly capable of doing full duplex
<mwk>
but you really really want to feel that half duplex experience
<mwk>
you can turn it on
<mwk>
also, yes, hubs
<mwk>
in theory you can have those on 100BASE-whatever
<whitequark>
I'm not even sure where 802.3 defines 100BASE-TX half duplex
<whitequark>
like, it sure *refers* to it a lot
<whitequark>
their idea of "let's define 100BASE-TX in terms of FDDI but also replace all terminology with that from 10BASE-T" is also not confusing at all
<whitequark>
oh i see, 100BASE-TX half duplex is still, well, half duplex, in that it uses two pairs, unlike 10BASE-Te, which is simplex
<whitequark>
so *that*s why you can have a passive 10BASE-T hub but not a passive 100BASE-TX hub