You basically can't daisy chain keyboard controller midi outputs - except there is a dedicated midi merge processing.
Well...
I actually have kind of a purposeful setup where I'm using the MIDI output of my Behringer BCF2K connected to the input port of my Roland A70 -- then the four out ports to individual ins on my 8-port interface. That's *kind* of daisy chaining outputs, but this is a very specific instance which essentially gives me 4 BCF2K's because the MIDI messages come into the computer on different ports.
And you can go Computer MIDI out -> Keyboard A MIDI in, Keyboard A MIDI out -> Keyboard B MIDI in, Keyboard B MIDI out -> Computer MIDI IN to have a daisy chained function because the MIDI spec insists on retransmitting all input to the output except for SysEx messages. But, each connection results in about a 1ms delay; not problematic with a first or second generation retransmit, but can be noticeable afterwards with particularly percussive chordings. The MAIN problem with this setup is making sure that Keyboard B doesn't errantly respond to MIDI messages from Keyboard A. You could work around this by using Keyboard A's MIDI thru to Keyboard B's MIDI in, (and Keyboard A's out goes to Computer MIDI IN) but you lose the ability of Keyboard B to control anything. The MIDI thru function is almost universally implemented as a hardware function of the standard hex optoisolator circuit, which for all intents and purposes is as close to a "hard-wired" copy of the input as can be achieved with an optical coupling device.
The best solution is to have a multi-port MIDI interface.
I must Agree on that one! To use different midi channels you must have different midi channels. By daisychaining midi devices simply allows you to send the same type notes!